Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.99.2
-
None
-
None
Description
When dealing with foreign key constraints, derby will print similar exceptions:
Exception: java.sql.SQLIntegrityConstraintViolationException Message: INSERT on table 'SQ_JOB_INPUT' caused a violation of foreign key constraint 'SQL130511152808250' for key (20). The statement has been rolled back
Constraint name SQL130511152808250 is auto generated because we are not explicitly naming them in the create script. For simpler debugging, I would suggest to explicitly name all constraints.
Attachments
Attachments
Issue Links
- links to