[
https://issues.jboss.org/browse/TEIID-5201?page=com.atlassian.jira.plugin...
]
Divyesh Vallabh commented on TEIID-5201:
----------------------------------------
I've attached an extract of log that contains the sql its trying to execute.
[^information_schema.log]
Ah, I had only checked on the pg_ tables mentioned in the issue. That
would require an additional system schema, so we'll have to give some thought to the
ramifications.
I was hoping the pg_ tables would have been sufficient to generate the meta information
for tables and views, but it seems the provider uses the information_schema instead. Doing
some research it seems there is a way to use PowerBi advance query features to extract the
data vs using the wizards.
If you agree I think this issue can still be marked as resolved because these changes does
allow for a session to be created and queries be executed against any vdb using the npgsql
provider. A separate issue can be created for tracking the information_schema support so
meta information can be queried.
Update teiid pg_type schema to match PostgreSQL pg_type in support of
NPGsql provider
-------------------------------------------------------------------------------------
Key: TEIID-5201
URL:
https://issues.jboss.org/browse/TEIID-5201
Project: Teiid
Issue Type: Bug
Components: ODBC, Query Engine
Reporter: Divyesh Vallabh
Assignee: Steven Hawkins
Attachments: babynametest.zip, information_schema.log
When using NpgSQL provider to connect to Teiid the connection fails because the
teiid.pg_type table does not contain the column "typreceive"
Add missing columns from Postgres.pg_type
(
https://www.postgresql.org/docs/9.2/static/catalog-pg-type.html) to teiid
Add missing columns from Postgres.pg_user
(
https://www.postgresql.org/docs/9.2/static/view-pg-user.html) to teiid
Add missing columns from Postgres.pg_constraint
(
https://www.postgresql.org/docs/9.2/static/catalog-pg-constraint.html) to teiid
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)