[
https://issues.jboss.org/browse/TEIIDDES-2570?page=com.atlassian.jira.plu...
]
Matus Makovy reopened TEIIDDES-2570:
------------------------------------
I came across a couple of issues with this dialogue.
When you define a unique constraint and you don't select any columns, the dialogue
displays an error message that there are no columns selected, but you can still hit OK
(button is not disabled).
Another one is that when you edit the constraint and then hit OK, the Edit button is
disabled and it never gets enabled again.
I will add a link to video.
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)