zende wrote: > I used SesionExtension.after_flush. Worked great. > > Thanks for the help Michael!
if you are using transactions with isolation, the changes within the transaction wouldn't be visible to other connections until commit, which implies after_commit() might be the better target - though you don't get a chance to sift through what's changed at that point. > > -- > > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to [email protected]. > 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. > > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. 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.
