On Wed, Apr 30, 2008 at 11:30 AM, Michael Bayer <[EMAIL PROTECTED]> wrote: > flush() always uses a transaction, so when your pdb process hits, the > transaction has not been committed yet and results are not visible > outside of the transaction. the "transactional" keyword on Session > does not mean "don't use transactions at all", it means "don't > automatically enter a transaction outside of a flush". Its been > renamed to "autocommit" in 0.5.
Ah, yeah, that would do it. Any suggestions for other hooks that might do what I'm looking for, or should I just handle this myself before and after the flush? -- david bonner [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
