[
https://issues.jboss.org/browse/TEIID-3042?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3042:
---------------------------------------
Usage was chosen to keep the table / column name concise:
CREATE FOREIGN TABLE Usage (
VDBName string(255) NOT NULL,
UID string(50) NOT NULL,
object_type string(50) NOT NULL,
SchemaName string(255) NOT NULL,
Name string(255) NOT NULL,
ElementName string(255),
Uses_UID string(50) NOT NULL,
Uses_object_type string(50) NOT NULL,
Uses_SchemaName string(255) NOT NULL,
Uses_Name string(255) NOT NULL,
Uses_ElementName string(255),
PRIMARY KEY (UID, Uses_UID)
);
The term usage was chosen as this was similar to a view in sql server and most other dbs
when you ask about dependency/referencing info give it in the other direction. That is
you are finding objects that depend upon the one you are asking about, not what that
object is dependent upon.
Other approaches include just exposing procedures (this is especially useful to constrain
how the information is searched and/or if something is computed).
expose dependency information in system tables
----------------------------------------------
Key: TEIID-3042
URL:
https://issues.jboss.org/browse/TEIID-3042
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
We should expose additional view/procedure and even column information in terms of their
dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)