db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian McCallister <bri...@apache.org>
Subject Re: Is HSQLDB compatible with ASF license?
Date Thu, 10 Feb 2005 15:42:17 GMT
(From general@incubator)

This would rock!

I've switched to Derby for embedded stuff, but the disk io is still to 
slow for decent unit testing. An in-memory flag would be awesome.

HSQLDB is great for unit testing as it supports completely in-memory 
database instances. They are extremely fast, and are implicitely 
destroyed when the last connection is closed, so you can create the 
database, create the schema, hold the connection, run tests against 
in-memory db, then close the connection, destroying the database -- for 
each test case and still have it be very fast.


On Feb 9, 2005, at 11:39 PM, Daniel John Debrunner wrote:

>> Hi all, I love Derby, but for unit testing it's just too slow. We used
>> to use HSQLDB before iBATIS joined ASF, but I switched to Derby it
>> because I wasn't sure if HSQLDB was compatible with the ASF license.
> There has been some discussion of adding a lower durability option to
> Derby, which would allow much faster database creation etc. for unit
> testing. Some internal testing flags already exist so I believe it's a
> fairly small amount of work to externalize them in a rational way. Come
> to the derby-dev list get involved to bring the issue up again (or fix
> it yourself)!
> I'm not sure how hsqldb can be used as a test database, given that
> multiple threads can overwrite each other, due to hsqldb only 
> supporting
> dirty read mode (no isolation). Thus if you see incorrect results it
> seems you have to work out if hsqldb is the problem or your 
> application.
> Dan.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org

View raw message