Jacek, Thank you very much for the reply. I am using an in-memory db, and I tried the property below with no success. Because the db is in memory, there's nothing to delete in the file system.
Cheers, -- Alex On Jan 6, 2008 5:44 PM, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > On Jan 6, 2008 11:42 PM, Alexander Saint Croix > <[EMAIL PROTECTED]> wrote: > > > Dain mentioned that I might completely drop and restart OpenEJB between > > tests. He also mentioned that OpenJPA might have a way to wipe the > database > > tables clean for a given persistence unit. > > Here's one possible solution for you - the usage of in-memory db and > <property name="openjpa.jdbc.SynchronizeMappings" > value="buildSchema(SchemaAction='add,deleteTableContents')" />. Until > an em is in use the tables are there in db. Once it's closed, at > openejb shutdown, the tables will get dropped automatically. You may > also want to remove the target directory where the db sits in. > > See > http://www.jaceklaskowski.pl/wiki/Zasady_zapisu_zmian_do_bazy_danych_w_JPA#Konfiguracja_JPA_-_persistence.xml > for some configuration settings. The article is about how entity > changes are persisted in db using different jpa providers and is > written in Polish, but the configuration files should be > well-understandable by non-Polish speakers too. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl >
