[
https://jira.jboss.org/jira/browse/TEIID-870?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-870.
----------------------------------
Resolution: Done
Updated the JDBC metadata as described and also implemented the getSchemas(catalog,
schemaPattern) method.
IMPORTANT: This change can break any direct usage of Teiid's DatabaseMetadata - e.g.
instead of using the vdb name as a schema pattern, it should be passed as the catalog.
And any searches using a table name should not include the model name as part of the table
name.
Standardize the JDBC metadata
-----------------------------
Key: TEIID-870
URL:
https://jira.jboss.org/jira/browse/TEIID-870
Project: Teiid
Issue Type: Sub-task
Components: JDBC Driver
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.0
The current JDBC metadata:
catalog = null
schema = vdbname (except when getSchemas is used, then it's reported as model name)
table = table full name
proposed change (which is much closer to what was done for OA ODBC metadata):
catalog = vdbname
schema = model name
table = the rest of the table name including "." if a schema/catalog is in the
model
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira