I am here at OSCON and a user of Derby was complaining rather energetically to me at the cost of startup time for Derby. He said this is a real problem for running unit tests, as this is compounded by running multiple tests, each one starting up a new database.

I was wondering if other users out there have a similar complaint and if you can give a sense of how important this is. If you can describe your specific usage pattern that would be very helpful.

Thanks!

David

Reply via email to