Seems I'm not the only one bitten by this. I need some pointers on how to debug this. For the record, I agree with the 0.4.3 change that explicitly raises these errors when an inactive transaction is acted upon.
What I want is a way to find the correct spot so I can make a smaller test-case, as I can't really ship my app around. http://groups.google.com/group/pylons-discuss/browse_thread/thread/cfd5aeb5cbf088cc > <class 'sqlalchemy.exceptions.InvalidRequestError'>: The transaction > is inactive due to a rollback in a subtransaction and should be > closed > > I think this is because of a foreign key violation that happens in > some prior step, and that leaves the connection in the pool in a funky > state. (But that's just a guess.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
