> I'm trying to setup a "safe" testing database environment for
> some unit testing of a web application. I would like to have
> the unit tests restore the database to a known state before
> every test. The simplest way I thought would be to have the
> testing tools drop/create the testing da
On Aug 2, 2005, at 11:33 PM, Tom Lane wrote:
"Eric D. Nielsen" <[EMAIL PROTECTED]> writes:
... simplest way I thought would be to have the testing tools drop/
create
the testing database on every test case, and then populate the
database from a specified file. However I don't want to give th
"Eric D. Nielsen" <[EMAIL PROTECTED]> writes:
> ... simplest way I thought would be to have the testing tools drop/create
> the testing database on every test case, and then populate the
> database from a specified file. However I don't want to give the
> test user superuser privileges. Thu
I'm trying to setup a "safe" testing database environment for some
unit testing of a web application. I would like to have the unit
tests restore the database to a known state before every test. The
simplest way I thought would be to have the testing tools drop/create
the testing database
