Michael Bayer wrote:
If finishing with a .remove() is a big deal in your environment, which
it seems like it is, you could do a .remove() at the start of the
request instead.
You really don't need the "remove()" if you have definitely called
commit() or rollback() last, and you have expire_on_commit=True. In most
cases the session will be empty on the next request.
When could it not be empty and would that matter?
Are there any other implications of calling neither .remove() nor
.close()? I have a (hopefully) paranoid worry about connections not
being returned to the pool and/or "going away" in typical MySQL style...
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
