[
https://issues.jboss.org/browse/TEIID-3379?page=com.atlassian.jira.plugin...
]
Camilo Ortiz commented on TEIID-3379:
-------------------------------------
Not sure if this problem also applies for dynamic VDBs, but I get duplicate constraints
using Teiid Designer when I try to create a source model for an Oracle DB using fully
qualified names. For example, if I have a table my_schema.my_table with the indices
my_index1 and my_index_2, Teiid imports the table and both of the indices with the same
name my_schema.my_table. In fact, this is a problem with only one index as it has the same
name as the table. This is no a problem if I dont use fully qualified names.
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)