]
Steven Hawkins commented on TEIIDDES-1246:
------------------------------------------
So then this is the second case, a unique constraint is standing-in for a primary key.
That should not be allowed. fks can only reference primary keys.
After changing model to replace primary key with a unique key, the
deployment of the vdb errors saying PrimaryKey does not exist
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1246
URL:
https://issues.jboss.org/browse/TEIIDDES-1246
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 7.4
Reporter: Van Halbert
Attachments: dummy-ds.xml, server.log, Trade.vdb
In designer, I removed a primary key and replaced it with a unique key, and changed the
foreign key to now reference the unique key, and all built with no errors. When deploying
vdb to server, you see this exception (partial, see attachment for full log):
Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist.
at
org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353)
at
org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: