Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-1042

Sqoop2: Name constraints in Derby repository

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.99.2
    • Fix Version/s: 1.99.3
    • Component/s: None
    • Labels:
      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

        1. bugSQOOP-1042.patch
          13 kB
          Jarek Jarcec Cecho

          Issue Links

            Activity

              People

              • Assignee:
                jarcec Jarek Jarcec Cecho
                Reporter:
                jarcec Jarek Jarcec Cecho
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: