[ 
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347722#comment-14347722
 ] 

Bryan Pendleton commented on DERBY-6773:
----------------------------------------

I have a feeling that maybe the package name is wrong for your new exception 
class;
if you have an incorrect package statement in your Java class, then other 
programs
which try to access that class can't find it, which leads to errors like the 
"cannot find symbol"
error that you pasted.

What does 'svn status' print for you?

Also, try running 'ant -verbose build all'; that should print more details 
about the build error.

I looked for the error message from 'svn diff' in your pastebin, but I only see 
the output
from the 'ant build all' command. Can you paste the result of running your 'svn 
diff' so
I can see that error too?

> 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
>
>
> 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)

Reply via email to