> it appears that they are binding their metadata to a connection > completely distinct from the one they bind their SessionTransaction > to, is generally disastrous for a straight SQL statement like > table.update().
This is something we should fix in the 1.x line, and make sure we don't replicate in the 2.0 transaction managment middleware when that gets built. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
