[
https://issues.jboss.org/browse/TEIID-2187?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2187.
-----------------------------------
Resolution: Done
corrected and added a release note that older ddl can replace CONSTRAINT with a comma to
be compatible. Starting with 8.2 you can use CONSTRAINT name ... to give a name to the
constraint.
However the DDL string logic will treat any single column UNIQUE/INDEX/PK/FK constraint as
not being named as it will be associated with the column.
The grammar reference will be updated later in the release and we'll need to regen the
diagrams in the DDL reference.
Constraint parsing is incorrect
-------------------------------
Key: TEIID-2187
URL:
https://issues.jboss.org/browse/TEIID-2187
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.0
Environment: Constraint parsing should follow the pattern:
([CONSTRAINT name] ... | PRIMARY KEY ...)*
rather than:
CONSTRAINT <constraint list>
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira