> > > It is possible we could re-introduce "check for open cursors" as a > pool events extension. It would raise an error if any connection is > returned with associated cursors still opened and could track down > issues like these. >
That would be a great diagnostic tool for this: It's hard to track down the issue now, as the problem doesn't show itself until the cursor is re-used on some later, unrelated query. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
