Don't know if this handles your needs, and I haven't tried it with Derby before, but DBUnit allows you to ensure your tables are in a known state prior to and following unit tests. It's very easy to use and makes unit testing code with SQL statements simple to manage.
Hope that helps. --- Colin Taylor <[EMAIL PROTECTED]> wrote: > Hi there, > > I would like to use Derby for my unit testing where > a testing snapshot > for the database is reverted to after each suite > of tests complete. > I believe I could do this my copying the data > directory but that seems > a bit heavyweight considering I'll have a lot of > suites for my 200+ > table schema which I will want to run in isolation. > > From an earlier thread http://tinyurl.com/4ebxq I > understand point of > time recovery is not supported but I could achieve > this effect with > log sequence numbers? Can anyone give me some > pointers on how i might > achieve this? Do I get a the current sequence > number at the start of > the test suite and then roll the log back to it when > the suites > finished. Or is there perhaps a way for my > inserts/updates/deletes to > only exist during the suites lifetime some how.. > > Cheers for any help > Colin. > The only "dumb question" is the one you were too afraid to ask. ________________________________________ Check out RouteRuler - Free software for runners, cyclists, walkers, etc. http://routeruler.sourceforge.net ________________________________________ Get a handle on your data with "pocOLAP", the "little" OLAP project http://pocolap.sourceforge.net ________________________________________ __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
