Yeah, I wouldn't expect one to survive a fork, in fact I was looking for a way to ensure that there were **no** open connections before a fork. Looking over the pool module, I guess when I said "fully closed pool", what I'm really looking for is a fully empty pool.
I'm going to try a call to engine.dispose() in the child after the fork, which should invalidate all the connections in the pool and force the pool to start making new ones and see how that works out. thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
