Mike, thanks, that did isolate concurrent connections immediately.
The problem is, I can't figure out how the hell I am generating a
concurrent connection!
It reports only one open connection, and that one connection never
closes, even though I close the session. It tries to open the second,
and fails (correctly).
Is there a better way to interactively probe the pool while it's
running?
How come localizing and deleting the engine object itself doesn't
close my connection? Maybe it closes but I never see the report of
that fact?
There's too much going on to which I have no visibility. Please show
me some good ways to probe the pool without modifying code in your egg
files.
Thank you for your time and help,
Gloria
--~--~---------~--~----~------------~-------~--~----~
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
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
