[sqlalchemy] Re: session close - whatfor?

2009-04-06 Thread Diez B. Roggisch
> not at all, when you commit/rollback, everything in the session is > expired (assuming you're on 0.5). 0.5.2 > Doing a remove() at the end of a > request is a good way to ensure nothing is around from the previous > request but in theory its not needed. But again, I've no idea what > TG does

[sqlalchemy] Re: session close - whatfor?

2009-04-05 Thread Michael Bayer
On Apr 5, 2009, at 3:34 PM, Diez B. Roggisch wrote: > > Michael Bayer schrieb: >> the close() will remove any objects left in the session and may >> help with >> unit tests in that the subsequent tests aren't interfered with by >> objects >> remaining from the previous test. > > Where is the

[sqlalchemy] Re: session close - whatfor?

2009-04-05 Thread Diez B. Roggisch
Michael Bayer schrieb: > the close() will remove any objects left in the session and may help with > unit tests in that the subsequent tests aren't interfered with by objects > remaining from the previous test. Where is the difference between a process running several tests and one answering se

[sqlalchemy] Re: session close - whatfor?

2009-04-02 Thread Michael Bayer
the close() will remove any objects left in the session and may help with unit tests in that the subsequent tests aren't interfered with by objects remaining from the previous test. but its better to use a distinct Session for each test and keep things simple. I keep hearing about Turbogears no