[
https://issues.jboss.org/browse/TEIIDDES-1660?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1660:
----------------------------------------
The "error" was the default EMF value for nullable is "NULLABLE",
which has been that way for 10 years.
So if no nullable value is defined in DDL it was ending up NULLABLE independent of any
PK/UC check.
We now check the PK/UC to make sure it's column is "NOT NULL".
DDL Importer should correct Primary Key referencing a nullable
column
---------------------------------------------------------------------
Key: TEIIDDES-1660
URL:
https://issues.jboss.org/browse/TEIIDDES-1660
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 8.1
Reporter: Mark Drilling
Assignee: Barry LaFond
Fix For: 8.2
If the DDL does not specify the nullability of a column, but the column is used as a
primary key, the DDL Importer should go ahead and specify that the column is not nullable.
If not this results in an error with the generated model.
--
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