[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-2890) Hibernate cannot wrap HSQLDB constraint violations exceptions

[Diego Pires Plentz (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Diego Pires Plentz resolved HHH-2890.
-------------------------------------

      Assignee: Diego Pires Plentz
    Resolution: Rejected

Closing as rejected since this is a HSQLDB issue and is solved in the next major version.

----------------------------------
from Fred Toussi <fredt at users.sourceforge.net>
--

Yes, when a batch update is not completely successful (when any of the batched statements is unsuccessful), the BatchUpdateException is thrown but the cause of the unsuccessful statement is not returned.
 
This has been improved in the code for the next major version, which also returns the code and error message for the failed statement.
 
Regards
 
Fred Toussi

> Hibernate cannot wrap HSQLDB constraint violations exceptions
> -------------------------------------------------------------
>
>                 Key: HHH-2890
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2890
>             Project: Hibernate3
>          Issue Type: Sub-task
>          Components: core
>    Affects Versions: 3.2.1
>            Reporter: Baptiste MATHUS
>            Assignee: Diego Pires Plentz
>            Priority: Minor
>         Attachments: UnitTestConstraintBug.zip
>
>
> Since I can't attach a file to a bug that hasn't been logged by me. I'll create a sub-bug, since logging a bug was anyway something I planned to do when I created the testcase.
> In the attached zip, you'll find a project that has two entities: Customer and Invoice. An Invoice references a Customer. I show that trying to delete a Customer that's referenced by an invoice doesn't throw a ConstraintViolationException with HSQLDB (1.8.0.7 or 1.7.3.3 gives the same result).
> The testcase is in the test package.
> I hope this helps tackle the problem. Before logging a bug in the HSQL tracker, I'd really appreciate to have your opinion. Shoud I do it?
> FYI, I tested the very same code on Oracle, and the ConstraintViolationException is very well thrown...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira