in-memory database issues

[novotny]

Hi,

I was using my own PersistenceManager singleton which wrapped a Hibernate SessionFactory and did a session.open and session.close for all db operations and then switched all my DAOs to extend from HibernateDaoSupport. I had also been using in-memory HSQLDB with Tomcat in a web application. What I noticed is that before the data would actually persist between successive Tomcat restarts, but now it seems it doesn't. It seems I now have to run HSQLDB in stand-alone server mode... is this normal?

Thanks, Jason

[novotny]

I should mention that the only difference is before I was using

hibernate.connection.url=jdbc:hsqldb:/database/gridsphere

to point to the flat file DB and now I've been forced to use

hibernate.connection.url=jdbc:hsqldb:hsql://localhost

in order for the data to be persisted between server restarts

[trisberg]

This is more of an HSQLDB question, but I know they now require an explicit shutdown command to be executed - was there anything in the log indicating the database was not shut down properly?

[novotny]

I never needed to do this before-- I've been using hsqldb 1.7.1.... shouldn't hibernate be sending it a command under the covers for me so I'm not exposed to db specific issues?

Thanks, Jason