[
https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin...
]
Mark Drilling commented on TEIID-2922:
--------------------------------------
Ok, I didnt realize that.
It does have a negative effect in the tooling tho. Import will result in a couple
validation errors - 1) same named siblings and 2) PK and UC reference the same columns.
Not sure how we're going to handle ATM
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