-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 3 posts ] 
Author Message
 Post subject: Hibernate 2.1.6 and HSQLDB 1.7.1
PostPosted: Mon Aug 30, 2004 5:34 pm 
Newbie

Joined: Mon Aug 30, 2004 5:25 pm
Posts: 2
I was wondering if there was a way to use Hibernate 2.1.6 with HSQLDB 1.7.1. I've run into bugs with HSQLDB 1.7.2 (Not hibernate) and would rather not revert back to Hibernate 2.1.4. Specifically the generation of the database schema using Hibernate 2.1.6 from the mapping file seems to require HSQLDB 1.7.2 now, and there seems only to be one HSQL dialect.


I didn't see anything on the forums or current documentation, so I figure it couldn't hurt to ask.


-Ned


Top
 Profile  
 
 Post subject:
PostPosted: Mon Aug 30, 2004 8:14 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 12:50 pm
Posts: 5130
Location: Melbourne, Australia
I found 1.7.2 to be overall more bugfree than 1.7.1. I actually don't even know of any bad bug in 1.7.2...


Top
 Profile  
 
 Post subject:
PostPosted: Tue Aug 31, 2004 11:57 am 
Newbie

Joined: Mon Aug 30, 2004 5:25 pm
Posts: 2
The problem I'm running in is with a parent-child one-to-many list that works fine with hsql 1.7.1, postgresql and oracle. hsqldb 1.7.2 gives an error on a delete of a child element, where it works fine in the other ones. (Specifically, hibernate does an 'update set parent_id = null and position = null before deleteing, hsqldb 1.7.2 throws an error saying 'invaid token' in the SQL update statement)

I'm trying to put together a test case that shows this. Hibernate only does this update (from what I can tell) if there are more then one child already mapped. No error is seen if there is only one child. Judging from what I saw in the HSQL log, and what hibernate is sending, nothing looks wrong from what hibernate is doing. That's the reason I think its in the HSQL layer.

So, judging from your response, there isn't a way to get Hibernate 2.1.6 to generate 1.7.1 compatiable SQL code for database creation then.... If you really believe that HSQL 1.7.2 cannot be to blame, let me know and I'll do a full post of the relivent sections of my stuff that is experiencing the problems.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 3 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.