Using Derby and Hibernate.

Derby has a backup and restore feature.

The backup feautre works as documented by using a connection's 'prepareCall' method.

Derby will restore the database using a modified connection URL of the form: 'jdbc:derby:testDatabase;restoreFrom=c:\mybackups\testDatabase'.

Placing this modified URL into the hibernate.cfg.xml file and re-running my application restores the database.

But, I don't want to have to shutdown my application, modify the hibernate.cfg.xml file and restart to get the backup restored.

I thought the key to make it work would be to shut down all hibernate connections I could think off such as session.close, flush, etc.

I then discarded my session factory and made a new one, however I first swapped my new URL for the old in the properties collection before I made the new session factory - like this:

Configuration configuration = new Configuration().configure();
configuration.setProperty("hibernate.connection.url", "jdbc:derby:testDatabase;restoreFrom=c:\mybackups\testDatabase");
sessionFactory = configuration.buildSessionFactory();

To bad for me, new session from the session factory works just fine, but the resulting information is not from the restored database but from the current one. It is like the actual database is never really closed and re-opened using the new URL.

Has anyone done this before or have clue how hibernate/JDBC might be out smarting me?

Thanks for your help.

kstotz

For public reference here is an answer I came up with: