[jira] [Updated] (DERBY-6773) Derby throws plain SQLIntegrityConstraintViolationException

["Abhinav Gupta (JIRA)" <ji...@apache.org>]

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

Abhinav Gupta updated DERBY-6773:
---------------------------------
    Attachment: ant -verbose build all.txt

Hi Bryan,

I am attaching the, 'svn diff' [0], 'svn status' [1]. And since 'ant
-verbose build all' is exceeding pastebin limit, I have attached it with
the mail. I had assumed that it will be in the same package as the
SQLIntegrityConstraintViolationException. I haven't written much in the new
class yet, but I think I have an idea on what to write.

[0] : http://pastebin.com/VT6JmLGM
[1] : http://pastebin.com/FJUn1Hwm

Thank you

On Thu, Mar 5, 2015 at 4:22 AM, Bryan Pendleton (JIRA) <ji...@apache.org>



> Derby throws plain SQLIntegrityConstraintViolationException
> -----------------------------------------------------------
>
>                 Key: DERBY-6773
>                 URL: https://issues.apache.org/jira/browse/DERBY-6773
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.10.2.0
>         Environment: Windows 7 x86_64, Java 1.6.0.45
>            Reporter: Jochen Wiedmann
>            Assignee: Abhinav Gupta
>            Priority: Minor
>         Attachments: DERBY6733Repro.java, ant -verbose build all.txt
>
>
> If a unique constraint is violated by an insert statement, then Derby throws an SQLIntegrityConstraintViolationException. The error message contains, in particular, the constraint name and the table name.
> To distinguish between cases with various constraints, Derby should instead throw a subclass of SQLIntegrityConstraintViolationException, with methods like getConstraintName(), and getTableName().
> See also https://hibernate.atlassian.net/browse/HHH-9516.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)