Doesn't the testdb.script file get loaded by hqldb every time? I remember from using hsqldb that this was a pain.. I don't want to ignore the testdb.script as we may need to edit the script, but on the otherhand I guess now it is going to prompt to be committed constantly.. What do you think of adding it to the unit test resources so it gets copied to /target/test-classes and then run from there, that way preserving the old one?
I know I have gotton around this by using Hibernate's ability to create sql scripts dymanically and load them, but that is real overkill! We could also look at the mckoi db, I used that to unit test as well.. Eric > -----Original Message----- > From: Emmanuel Bourg [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 18, 2004 7:54 PM > To: Jakarta Commons Developers List > Subject: Re: [configuration] DatabaseConfiguration > > > I noticed you've added a .cvsignore in the conf directory, I > think you > can add the testdb.script file in the ignore list as well, it's being > rewritten on every test run but the changes shouldn't be committed. > > Emmanuel Bourg > > > Eric Pugh wrote: > > > I have gone ahead and committed this. It is defintily an > implementation > > that we have been needing! Could you maybe look at the > Simian report. there > > are a couple duplications listed, that I think look like > they could be > > extracted into their own method without being too confusing. > > > > ERic > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
