The problem you are (probably) having is one process creates the db, but a different one is running the tests - so the db "dissapears" - in memory db only lives in the process in which it is created.
you could try modifying the build.xml and change all "fork" parameters to "false" to force all running in a single process... Russell > -----Original Message----- > From: Marcus Ahnve [mailto:marcus.ahnve@;lecando.com] > Sent: Thursday, October 17, 2002 3:31 PM > To: [EMAIL PROTECTED] > Subject: Hsqldb in memory > > > Has anyone managed to Hsqldb in memory? My idea was to unittest using > jdbc:hsqldb:., but after creating the db I get a "table can't > be found" > error on the insert statement. Using disk based hsqldb works smoothly. > > On a related note, has anyone used in Axion with the same intention? > > Regards /Marcus > > > -- > To unsubscribe, e-mail: > <mailto:ojb-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:ojb-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
