On Jan 25, 6:05 pm, Daniel Moisset wrote:
> > I think that should work. It would be great to write this in a way
> > that just checks if the connection supports savepoints. If not, then
> > run the tests in the old-fashioned way, if yes, do the above trick.
>
> OK, I can change that... there are a
On Tue, Jan 24, 2012 at 2:22 AM, Anssi Kääriäinen
wrote:
> On Jan 24, 3:07 am, Daniel Moisset wrote:
>> [1] The idea is loading fixtures once per TestCase instead of once per
>> test method, and use DB rollbacks after each test to return the DB to
>> the after-fixtures-just-loaded state.
>
> So,
On Jan 24, 3:07 am, Daniel Moisset wrote:
> [1] The idea is loading fixtures once per TestCase instead of once per
> test method, and use DB rollbacks after each test to return the DB to
> the after-fixtures-just-loaded state.
So, the idea is to do the following for each TestCase:
begin
load fix
Somewhat independently from the recent thread, I had been working in
getting tests running faster. I essentially reimplemented an idea that
Erik Rose[1] posted here last year, but I did it in a way that I think
is more DB independent (although... I'm using it and have tested it
only under PostgreSQ
