db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6773) Derby throws plain SQLIntegrityConstraintViolationException
Date Thu, 29 Oct 2015 07:25:27 GMT

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

Jochen Wiedmann updated DERBY-6773:
-----------------------------------
    External issue URL: https://hibernate.atlassian.net/browse/HHH-9516
         Fix Version/s: 10.12.1.2

> 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
>             Fix For: 10.12.1.2
>
>         Attachments: CallSuper.diff, DERBY6733Repro.java, IntegrityConstraint.diff, SamePackage.diff,
SharedException.diff, addToTestSuite.diff, ant -verbose build all.txt, generateOnClientDoesntWork.diff,
passesTests.diff, subPart1.diff, subPart2.diff, switchArgs.diff
>
>
> 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)

Mime
View raw message