[
https://issues.jboss.org/browse/TEIID-3064?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3064:
---------------------------------------
The resolution I was thinking of was for Access. In that case getForeignKeys is a
completely unsupported operation by the bridge/underlying logic, so we made the default
for import to not import foreign keys and exclude problematic system tables. Here it
seems simple enough just to add a documentation note to specify the target schema that you
want, otherwise there can be issues with system metadata.
Sybase metadata loading fails
-----------------------------
Key: TEIID-3064
URL:
https://issues.jboss.org/browse/TEIID-3064
Project: Teiid
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.7
Reporter: Filip Elias
Assignee: Steven Hawkins
Attachments: server.log
Sybase metadata loading fails[1] when deploying dynamic vdb.
The problem is in JDBCMetdataProcessor.getForeignKeys. Method loads FKs from all tables,
but it fails when it tries to load FKs from table sysquerymetrics. The problem seems to be
that sysquerymetrics is not a system table, it is a view.
[1] Reason:TEIID11010 com.sybase.jdbc4.jdbc.SybSQLException: No such object or user
exists in the database.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)