db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6800) Implement DerbySQLIntegrityConstraintViolationException class
Date Sat, 18 Jul 2015 18:28:04 GMT

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

Bryan Pendleton resolved DERBY-6800.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 10.12.0.0

I believe we've completed the work we intended for this sub-task.

> Implement DerbySQLIntegrityConstraintViolationException class
> -------------------------------------------------------------
>
>                 Key: DERBY-6800
>                 URL: https://issues.apache.org/jira/browse/DERBY-6800
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>            Reporter: Bryan Pendleton
>            Assignee: Abhinav Gupta
>            Priority: Minor
>             Fix For: 10.12.0.0
>
>         Attachments: subPart1.diff
>
>
> As part of DERBY-6773, we wish to build a new exception class,
> to be named DerbySQLIntegrityConstraintViolationException,
> which extends java.sql.SQLIntegrityConstraintViolationException
> but provides additional methods getConstraintName() and
> getTableName().
> This exception will be thrown by the SQLExceptionFactory classes
> in the client and in the engine, instead of the current code which
> throws SQLIntegrityConstraintViolationException



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

Mime
View raw message