[
https://issues.jboss.org/browse/TEIID-4565?page=com.atlassian.jira.plugin...
]
Steven Hawkins reassigned TEIID-4565:
-------------------------------------
Fix Version/s: 10.x
(was: 10.0)
Assignee: (was: Steven Hawkins)
In looking at this again, it doesn't yet make sense to promote this to a system table.
The mixing of metadata record types (all_objects for example for oracle contains only
schema objects, no columns), optionally excluding system information as shown in the
example, the level of denormalization needed for search (including the description,
parent, and schema information), etc. are all things which probably need more discussion
or can just be defined as view for now. If we get more votes/contributions toward this,
then it will be included.
Add objects table to system schema
----------------------------------
Key: TEIID-4565
URL:
https://issues.jboss.org/browse/TEIID-4565
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Tom Johnston
Fix For: 10.x
The addition of a objects table would make it simpler to join to when extensions are
implemented.
An example might be something similar to this query:
select sysObjects.*
from (
select t.schemaName as Parent,t.name, t.uid ,'Table' as ObjectType
from sys.tables t
where schemaName not in (select distinct(schemaName) from
"SYS"."Tables" where isSystem = true)
UNION
select c.tableName as Parent,c.name, c.uid,'Column' as ObjectType
from sys.columns c
where schemaName not in (select distinct(schemaName) from
"SYS"."Tables" where isSystem = true)
UNION
select null as Parent,e.Value as Name,e.uid,'Property' as ObjectType
from sys.properties as e) as SysObjects
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)