You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the test case RMLTC0009c drops a referenced table before dropping the table that registered the foreign key. When running this test twice in a row, this can result in an a foreign key exception in some RDBs.
I propose to reorder the SQL script such that this conflict cannot occur:
DROPTABLE IF EXISTS test.Student; -- reorderedDROPTABLE IF EXISTS test.Sport; -- reorderedCREATETABLESport (
ID integer,
Name varchar (50),
PRIMARY KEY (ID)
);
CREATETABLEStudent (
ID integer,
Name varchar(50),
Sport integer,
PRIMARY KEY (ID),
FOREIGN KEY(Sport) REFERENCES Sport(ID)
);
INSERT INTO Sport (ID, Name) VALUES (100,'Tennis');
INSERT INTO Student (ID, Name, Sport) VALUES (10,'Venus Williams', 100);
INSERT INTO Student (ID, Name, Sport) VALUES (20,'Demi Moore', NULL);
The text was updated successfully, but these errors were encountered:
Currently, the test case RMLTC0009c drops a referenced table before dropping the table that registered the foreign key. When running this test twice in a row, this can result in an a foreign key exception in some RDBs.
I propose to reorder the SQL script such that this conflict cannot occur:
The text was updated successfully, but these errors were encountered: