[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352054#comment-14352054
]
Abhinav Gupta commented on DERBY-6773:
--------------------------------------
Hi Bryan,
I checked all the jars and none of them except derby.jar has the file
org.apache.derby.impl.jdbc, so I think that shouldn't be the problem.
In my classpath, I have
C:\Users\abhinav\trunk\jars\sane\derby.jar
C:\Users\abhinav\Documents\db-derby-10.11.1.1-bin\lib\derbyrun.jar
I had added db-derby-10.11.1.1-bin\lib\derbyrun.jar earlier last month when
I was still figuring out how to build the code. But now if I remove it or
replace it with the derbyrun.jar present in trunk.jars.sane, in both the
cases I get the error[0]. It's very puzzling to me as I had assumed that
derbyrun.jar would be identical from both the sources. Also I am confused
if derbyrun.jar should be in the classpath, should it be there ?
[0] : http://pastebin.com/0gcLNsJ1
On Sat, Mar 7, 2015 at 10:36 PM, Bryan Pendleton (JIRA) <[email protected]>
> 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)
