[
https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2922:
---------------------------------------
Some databases report primary keys both as a key and as a unique constraint, so it does
have two entries when we ask for get keys. Beyond clutter though, this doesn't have
any negative effect - other than rippling the same double entry through our metadata.
Extra unique constraint in dynamic vdb schema
---------------------------------------------
Key: TEIID-2922
URL:
https://issues.jboss.org/browse/TEIID-2922
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 8.4
Reporter: Mark Drilling
Assignee: Steven Hawkins
I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table
with only a primary key. See steps to reproduce.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira