]
Matus Makovy commented on TEIIDDES-2570:
----------------------------------------
Here is the video:
Is this unique constraint definition relevant only in Source model ? I am asking because
when you try to create new table and new unique constraint in View model, there is still
the old dialog page for unique constraints.
RelationalTable contains methods for single UniqueConstraint and
collection of UniqueConstraints
------------------------------------------------------------------------------------------------
Key: TEIIDDES-2570
URL:
https://issues.jboss.org/browse/TEIIDDES-2570
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export, Patch Release
Affects Versions: 9.0.1
Reporter: Paul Richardson
Assignee: Barry LaFond
Fix For: 10.0.1, 9.2.1
Attachments: edit-unique-constraint-dialog.png, unique-constraint-tab.png
While round tripping DDL import and export, the RelationalTable is used to store table
unique constraint. The DDL Importer stores the new constraints in the uniqueConstraints
collection. However, when saving the model to the BasicTableImpl instance, it actually
only looks at the single uniqueConstraint so values are lost.
Dynamic Vdb work has united these fields but retained the getUniqueConstraint() and
setUniqueConstraint() methods for backward compatibility with the
RelationalTableEditorPanel and ViewTableEditorPanel. These methods are deprecated and the
panels should be fixed to support entering multiple unique constraints.