Bug report SQL DEVELOPER DATA MODELER

Question

Hello,
I think i found a bug using Sql developer data modeler 2.0.0 build 584.
When importing a DDL file to create a relational model, foreign key constraints might not be created if foreign key uses multiple-field and the fields are not referenced in the same order as the primary key was.
ex:
Table FOO ..... PRIMARY KEY (id_1, id_2)
FOREIGN KEY (id_2, id_1) REFERENCES FOO (id_2, id_1)
Benjamin
P.S: Bellow is a portion of SQL code demonstrating the problem:
-- "_decompte"
CREATE TABLE "_decompte"(
numero_rang VARCHAR2(2),
numero_contrat VARCHAR2(13),
id_decompte VARCHAR2(19)
ALTER TABLE "_decompte"
add CONSTRAINT pk_decompte PRIMARY KEY (numero_rang, numero_contrat, id_decompte);
-- "_decompte_detail"
CREATE TABLE "_decompte_detail"(
numero_rang VARCHAR2(2),
id_ligne NUMBER(4),
numero_contrat VARCHAR2(13),
id_decompte VARCHAR2(19)
-- "_decompte_detail"
-- NOT Recognized by SQL DEVELOPER DATA MODELER (fields are not in the same order as primary key definition)
ALTER TABLE "_decompte_detail"
add CONSTRAINT fk_decompte_detail_1 FOREIGN KEY (numero_contrat, numero_rang , id_decompte) REFERENCES "_decompte"(numero_contrat, numero_rang , id_decompte);
-- Recognized by SQL DEVELOPER DATA MODELER
ALTER TABLE "_decompte_detail"
add CONSTRAINT fk_decompte_detail_2 FOREIGN KEY (numero_rang, numero_contrat, id_decompte) REFERENCES "_decompte"(numero_rang, numero_contrat, id_decompte);

Answer 1

Hi,
Well, I was recently given some database scripts and asked to correct and improve them. These scripts were not generated but rather hand made. Having no access to a DBMS I was just curious about the result of this option in Data modeler and tried it for a better DB overview. I don't need it at all, but I was surprised to discover that the result was a failure. So I tried various scripts until I found the mistake.
regards.