I don't think so.
We need it to work on the NH build server at a given point in time. I don't
think it needs to be portable to other servers. That is, while I'm sure it
would be valuable, I doubt we'll be using a different server anytime soon,
so we won't receive any of the value.
-----Original Message-----
From: Patrick Earl
Sent: Thursday, October 06, 2011 6:38 AM
To: nhibernate-development
Subject: [nhibernate-development] Re: Test Database Creation
Is the answer to this affected by Oracle on the build server? Do we
need to do #1 to be consistent?
On Mon, Sep 5, 2011 at 8: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
