Details
-
Bug
-
Resolution: Done
-
Major
-
2.3.0.Final
-
None
Description
The primary key in the below DDL, customerfamilyhistoryid_pk, is created but does not have the reference to the customerfamilyhistoryid column. A similar issue, MODE-815 (which dealt with the UNIQUE keyword), has already been fixed. This column constraint is different in that it uses the "PRIMARY KEY" keywords but the fix will be pretty much the same. The only class affected is StandardDdlParser. A related defect, TEIIDDES-550, depends on this being fixed.
CREATE TABLE CustomerFamilyHistory
(
customerfamilyhistoryid number(10) CONSTRAINT customerfamilyhistoryid_pk PRIMARY KEY,
firstname varchar2(50) NOT NULL,
lastname varchar2(50) NOT NULL,
age number(3),
sibling varchar2(20),
customerid number(7) NOT NULL
);
Attachments
Issue Links
- blocks
-
TEIIDDES-550 Import DDL to Relational Table misses columns for primary, foreign keys
- Closed
- is related to
-
MODE-815 DDL Sequencer doesn't populate primary key correctly when constraint defined on a column
- Closed