[teiid-issues] [JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963120#comment-12963120 ] 

Steven Hawkins commented on TEIID-2922:
---------------------------------------

Mark, did you ever see if there is special handling on the Designer side for MySQL?

We are very lenient currently with constraint names.  They are effectively scoped to the table - but not even tracked by name.  It may be a good idea though to introduce this restriction.
                
> 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