On Apr 11, 2012, at 1:24 AM, Paddy Mullen wrote: > > The problem I have run into is, listening for "after_insert" on a subclass > extending DeclarativeBase, only results in calls after insert has been called > for, but not after it has been executed.
I'm not familiar with this behavior, can you illustrate ? after_insert happens after all INSERT statements for that particular entity. are you not observing that? -- 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.
