[jira] [Updated] (SQOOP-1042) Sqoop2: Name constraints in Derby repository

["Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SQOOP-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Jarcec Cecho updated SQOOP-1042:
--------------------------------------

    Attachment: bugSQOOP-1042.patch
    
> Sqoop2: Name constraints in Derby repository
> --------------------------------------------
>
>                 Key: SQOOP-1042
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1042
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.99.2
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.3
>
>         Attachments: bugSQOOP-1042.patch
>
>
> When dealing with foreign key constraints, derby will print similar exceptions:
> {code}
> 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
> {code}
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira