I could have sworn I saw conflicting behaviour. My after_insert would run, and the instance would have an id, it would then enqueue a task in celery. On the other side (in another process), celery would run that task, make a query against that database for that ID, and the ID wouldn't be in the database.
I think I can reproduce this in a single process too. I hope this is an error in my code. Let me work on a testcase. Thanks, Paddy On Wednesday, April 11, 2012 11:27:17 AM UTC-4, Michael Bayer wrote: > > > 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 view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/ex-ESCyj7QoJ. 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.
