Hi Michael, Thanks for your persistence :)
I've searched through my app, & we don't seem to have any calls to fetchone(), so I'm not sure what else to look for, but I'll try to do some debugging with ResultProxys, & see if that leads to any possible answers. On a side note, in our Pylons development.ini, we have these settings: sqlalchemy.default.max_overflow = -1 sqlalchemy.default.pool_size = 32 Is there anything there that could be having an effect on this? On Apr 25, 2:21 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > only if youre leaving dangling ResultProxys opened with pending > results, which should be a fairly rare occurence in a normal > application. if you simply call fetchall() on results instead of > fetchone(), that alone would eliminate any hanging cursors. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
