[
https://issues.jboss.org/browse/TEIID-3379?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-3379.
-----------------------------------
Resolution: Done
Found a reproducing case. If there are two foreign keys (at least one composite) to the
same primary key then the old logic could add multiple keys with the same name. This is
because the results are ordered by primary key and then sequence number - and not by fk
name.
Import error reporting duplicate constraints
--------------------------------------------
Key: TEIID-3379
URL:
https://issues.jboss.org/browse/TEIID-3379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.8
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
With TEIID-2922 it is now possible for metadata import to throw an exception when
multiple constraints are found with the same name even erroneously - see comments on
TEIID-2875.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)