Ive committed this fix in r3425. remove() calls close() on an existing session if one is present.
On Aug 29, 2007, at 6:49 PM, jason kirtland wrote: > > Jian wrote: >> >> the remove is described in doc as close + extra cleanup >> Shouldn't the doc be updated to add that point, which will make >> the the life of newbies like me easier =D >> Or better: add the explicitly close in remove. > > Yeah, the current remove() implementation in trunk isn't yet in > sync with the docs. I'm not sure if it is simply not complete or > if the feature is in flux... It will get resolved one way or > another before the next beta. But for now, I'm pretty confident > that having that explicit close() in there won't hurt you going > forward. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
