[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2890?page=c...
]
Baptiste MATHUS commented on HHH-2890:
--------------------------------------
For information, yesterday I tried to build HSQLDB myself to get rid of the problem, but
it was impossible since HSQLDB code available from public svn repository is NOT the latest
hsqldb code...
See
http://sourceforge.net/mailarchive/forum.php?thread_name=5623467908022508...
Copy of the thread FTR:
Re: [Hsqldb-user] Problem with batch statements still present ?
From: fredt <fredt@us...> - 2008-02-25 18:36
Attachments: Message as HTML
Our Subersion repository doesn't contain the very latest code.
The first alpha will be released soon (probably 2 weeks), and the SVN updated at the same
time.
Fred
----- Original Message -----
From: Baptiste MATHUS
To: hsqldb-user@li...
Sent: 25 February 2008 16:14
Subject: [Hsqldb-user] Problem with batch statements still present ?
Hi all,
As I was having a problem using HSQLDB with Hibernate, I logged this bug :
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2890
Then a Hibernate developer asked for more information on this list:
http://sourceforge.net/mailarchive/message.php?msg_id=7940ccb20710250415m...
Fred Toussi explained that it had been corrected in the "next major version" :
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.
Wanting to test this improvement, I just checkouted the latest hsqldb revision (402
precisely) from the hsqldb svn repository and built it myself.
But unfortunately, using it inside my project instead of the "old" 1.8.0.7 jar
does not seem to change anything :-/.
If you wish, I could do more tests if it should work.
But before doing so, I preferred asking here if checkouting the latest revision of the
repo (from
https://hsqldb.svn.sourceforge.net/svnroot/hsqldb/base/trunk) should actually
have corrected the problem, or if I should checkout from some other place.
Cheers.
Thanks a lot.
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira