[
https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2922:
----------------------------------
Fix Version/s: 8.8
I think that it does make sense to ensure named constraints have a unique name (at the
table scope), so we'll add a validation rule on our side for that.
This also means that we will need to address mysql returning the primary key in two ways.
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
Fix For: 8.8
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 was sent by Atlassian JIRA
(v6.2.3#6260)