Oh, thank you very much, that makes sense to me (and I knew I am wrong
somewhere because there are even tests for those after_flush events that
work).
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To view this discussion on the web visit
The flush events only fire off if there's actually something to be flushed. It
would be inefficient for the events to be emitted for every flush() as flush is
in fact called a great number of times, on every query, assuming autoflush
enabled. For this reason a flush() with a session that has
I've created this question at stackoverflow
http://stackoverflow.com/questions/6476652/sqlalchemy-0-6-5-and-0-6-8-sessionextension-after-flush-doesnt-gets-called
, but I thought maybe I should also ask here.
I don't get it, but this code doesn't call
