I've being using hibernate 3.2.4.sp1 + Hibernate Annotation 3.3.0.ga1 + hsql - 1.8.0.7 (standalone mode) as a lightweight backend for a small swing desktop application.

I initialize hibernate using the standard HibernateUtil approach (which keep a static SessionFactory). everything works fine except data doesn't get written to the db file couple of seconds after the transaction. so If I start up the program and write some record to db and exit program immediately, nothing gotten written to db. If I watch the file closely, seems it takes 6-8 seconds until HSQL actually write the file after the transaction commit.

I tried every possible setup properties for HSQL, for example, I set jdbc_batch_size to 0, and set connection.pool_size to 1. just fix this problem at all.

here's my hibernate.cfg.xml

The connection.url is set later in HibernateUtil


Any Thoughts? Thanks a lot

Hi onsight,
I'm stucked with the same problem you got.

I was working on an SWT application that was using an older version of HSQL. I upgraded the version of HSQL to 1.8.0.7 as you and also the version of Hibernate to 3.2.4.sp1.

Now if I modify some records and exit immediately the changes aren't written in the DB.

Have you find any solution?

Thanks for any suggestion!

Hi all,
I searched around and make some tests but I have still the same problem: hibernate don't save on DB.

I'm working on an SWT application that uses Hibernate and HSQLDB.
When I was working with HSQLDB version 1.7.2.11 and Hibernate 3.0.5 everithing was ok, but when i upgraded to HSQLDB version 1.8.0.7 and Hibernate 3.2.5 I found that my changes weren't saved on DB.

I tried various version of HSQLDB and Hibernate, but the problem still remain because I have to use a version of HSQLDB >= 1.8.0.2

Here is my hibernate.cfg.xml:




And here there is a simple test:



If I run this snippet two times the first output should be the first time 333 and the second time it should be 1335, but it is not!

No errors given from hibernate...

Thanks for any ideas,
Luca.

What is the actual logic that isn't saving? Please paste code regarding the save operations. From the code snipit you provided, you are updating the value in your example that you pasted, but you never call save on the object. You should be calling:



All your code should do is make the state of the TSpValOggGlobStima dirty. As far as why the output does not change on your system outs, I would look at the setter on the your VO to make sure that it actually is setting the internal property.

hi,
I have similar problem with updated data not refersh even the code call save() function.

Environment: Hibernate 3.2.5, Ehcache1.3, spring2.0 and jboss4.2.1

when I update a status to a current data and call save on the object. I retrieve data (find) from the same table for display. But the resultlist is still contained the old data. The updated data is still in the list.
It works in 3.1.3, the status was updated and when call find the latest resultlist is returned.
But in 3.2.x, the updated data still in the resultlLst after another select (find) utile I manually reload the page.

here is some code example:

//daoCustomerContent is a hibernate data object
customerContent.setCustomerContentStatus("SUBMITTED");
daoCustomerContent.save(customerContent);//save
// hibernate find
getHibernateTemplate().executeFind(new Page(_queryString, _values, _page, _pageSize));
// the update data update to "submitted" still exist in this result List


please advice, Thank you

Glad to know there are people out there struggling on problems like mine,
here's a typical save I do in my code



And I aways close SessionFactory when the applicatoin shutdown

Hi bradsdavis,
Thanks for your reply, but the problem still remain if i call



The object loaded from session.get() is in a persistent state yet, and if I call transaction.commit() the changes should be written in the database also without calling session.save(), I think. Am I wrong?
Anyway I don't see any change using the two methods.

Now I will try other version of Hibernate to see if this is the cause of this problem.

See you soon!

Well,
I tried different combination of HSQLDB and Hibernate.

The solution that worked for my small test is using HSQLDB version 1.7.3.3 and Hibernate version 3.0.5.

If I try to use a version of HSQLDB >= 1.8.0.1 the changes aren't written in the DB, but I get no errors. If I try to use a version of Hibernate >= 3.1.3, Hibernate can't find the tables.

Is there some change that I have ignored upgrading the version of HSQLDB?

I have to use a version of HSQLDB >= 1.8.0.2, I can't think that such a problem is a bug! What I'm doing wrong?

Help, please.

Hi,

I find some interesting information in the documentation about WRITE_DELAY
and changed made from version 1.7.2.
In particular setting WRITE_DELAY to FALSE solved my problems and changes are immediately written on the database.

SQL command:


N.B. If I open the database in server mode everything is ok, but I have to use standalone mode.

Hope this help, bye!

Environment: Hibernate 3.2.5, Ehcache1.3, spring2.0 and jboss4.2.1 and Oracle9. Not use HSQLDB

Hibernate 3.2.3 or later version + Spring Frame 2.0.

In hibernate 3.1 version, the data updated and return a correct new resultset.
in hiber nate 3.2.3 or later, the data updated but the resultset didn't get refresh. if I reload the page, the resultset is updated.

//daoCustomerContent is a hibernate data object
customerContent.setCustomerContentStatus("SUBMITTED");
//save: spring framework, hibernate3 DAO support
//getHibernateTemplate().saveOrUpdate(_entity)
daoCustomerContent.save(customerContent);//save
//select spring fram work hibernate3 DAO support

org.springframework.orm.hibernate3.support.getHibernateTemplate().executeFind(
new Page(_queryString, _values, _page, _pageSize))

// the update data update to "submitted" still exist in this result List


does hibernate 3.2.3 or later compatible with spring Frame work 2.0.6?



thank you

hi, all

subject : update data not refersh in hibernate 3.2.3 or later version

In Hibernate3.1 the data update gets refresh immediately with call flush() BUT it seems like 3.2.3 or latter require flush() to avoid update delay.

after I added super.getHibernateTemplate().flush(); afer I call save().
all date refresh immediately.


thanks

I'm only addressing the HSQLDB-specific issues, not whether and when Hibernate flushes. I'm a member of the HSQLDB development group.

For cases where a HSQLDB :file: URL is used with the shutdown connection property, I believe the root problem is that one or more of the intervening products (app server, ORM, data pooling) do not close all physical connections to the database when the app is stopped, or before JVM exit. The worse offender I have witnessed is Hibernate, which starts up an undocumented managing connection when you initiate your factory, and this connection is not closed when the using application is shut down. A work around is to turn down WRITE_DELAY so that even when there is no clean shutdown, your changes will still be persisted.

For cases where a HSQLDB :hsql: URL is used, the problem is not with the client-side :hsql: setup, but with the HSQLDB server-side setup. Unless you are running a distributed app server, your app code would be more straight forward and efficient by using :file:, regardless of whether you run a HSQLDB server to provide for remote access. If you are running a distributed app server and need to use :hsql:, it would very likely improve your design to run your HSQLDB server in a standalone JVM, especially if you are experiencing problems like those in this thread. (Depending on how hsqldb.jar is bundled and your app server's class loading strategy, you could hit visibility issues when using :file:). If you run your HSQLDB Server standalone, you can troubleshoot database problems and tune your DB independently of pooling, app server, ORMs, etc.