[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352223#comment-14352223
]
Abhinav Gupta commented on DERBY-6773:
--------------------------------------
Hi Bryan,
I tried deleting the files, but I didn't find the dir edb, derbydb in the
DerbyRepro directory and the derbydb dir in the
/p4clients/svnmain/client7/trunk/systest/out142,
though dir edb was present. I felt I had somehow managed to screw my source
code, so I downloaded the code again and applied the patch and the changes
we had done till now. Right now I am facing a new error, which I have a
feeling is similar to the one faced earlier [0]. And I am not sure if I
have solved the error of different version, I just have
trunk.jar.sane.derby.jar in the classpath now.
[0] : http://pastebin.com/U7WEDhxB
> 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, SamePackage.diff, 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)
