On Aug 31, 1:33 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > I dont think theres a connection pooling issue; its just that the > Session being remove()'d still references a checked out connection, > which has been fixed in the latest trunk. please issue Session.close > () before Session.remove() as a workaround for now. if problems > persist, let me know; theres some other things we can look at.
SA trunk works great, less real postgres connections used, and no overflow/connection problems so far! - Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
