[
https://issues.jboss.org/browse/TEIID-5307?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5307.
-----------------------------------
Resolution: Done
Added the views along with the others under the pg_catalog. While these are general
enough that they could be sys, we'll keep them together for now. There is a potential
issue with constraint naming. Teiid effectively allows constraints to be table/view
scoped, rather than schema scoped. So just referencing a constraint by
catalog/schema/name may not be sufficiently unique. If that is an issue, then we'll
need to project an alternative name here that is qualified in some way by the table.
Add views referential_constraints, key_column_usage,
table_constraints to information_schema
--------------------------------------------------------------------------------------------
Key: TEIID-5307
URL:
https://issues.jboss.org/browse/TEIID-5307
Project: Teiid
Issue Type: Enhancement
Components: ODBC, Query Engine
Reporter: Divyesh Vallabh
Assignee: Steven Hawkins
Fix For: 10.3
Outside of what is reference in npgsql provider, it seems as though PowerBI also
references following views to generate schema information
Add column in information_schema.columns
* data_type
Add support for information_schema.referential_constraints (
https://www.postgresql.org/docs/current/static/infoschema-referential-con...)
to teiid
Add support for information_schema.key_column_usage (
https://www.postgresql.org/docs/current/static/infoschema-key-column-usag...) to
teiid
Add support for information_schema.table_constraints (
https://www.postgresql.org/docs/current/static/infoschema-table-constrain...) to
teiid
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)