Isn't #1 exposing a potential maintenance headache in re: keeping this custom SQL synchronized with the DB objects? The present scorched-earth policy at least has the benefit of being certain there are no orphaned DB objects when run. What's the goal behind changing this? Speed/Perf of test-runs? Or other?
#2 makes good sense to me. Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Mon, Sep 5, 2011 at 10:03 PM, Patrick Earl <[email protected]> wrote: > Regarding NHibernate.TestDatabaseSetup, I'm thinking of implementing > one of the two following things: > > 1. Instead of dropping and recreating everything, execute custom SQL > for each database to drop every known type of object created by the > tests. > 2. Just make the existing code more robust, so it handles different > databases specified by the connection strings. > > What do you guys think? > > Patrick Earl >
