Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 4 Mar 2015 19:26:38 +0000 (UTC)
From: "Abhinav Gupta (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12757165.1416670280000.818.1425497198433@Atlassian.JIRA>
In-Reply-To: <JIRA.12757165.1416670280000@Atlassian.JIRA>
References: <JIRA.12757165.1416670280000@Atlassian.JIRA>
 <JIRA.12757165.1416670280617@arcas>
Subject: [jira] [Commented] (DERBY-6773) Derby throws plain
 SQLIntegrityConstraintViolationException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Abhinav Gupta commented on DERBY-6773:
--------------------------------------

Hi Bryan,

The error that I am getting is [0]. I had added the java class using the
'svn add' and 'svn propset' command. I have a feeling that I might be
making a basic mistake. I tried executing  'svn diff > d6773.diff' and I
got the same error.

I haven't completed writing the new exception class, I've a rough idea on
what to write. Right now, I wanted to see the arguments that are being
passed to the new class but I'm unable to build the code.

[0] : http://pastebin.com/DQuY2jqu

On Wed, Mar 4, 2015 at 8:33 PM, Bryan Pendleton (JIRA) <jira@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
>
>
> 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)