Am 09.01.2013 17:20, schrieb Michael Bayer:
> the after_commit() event is independent of any flush, so the last event
> where the history API still reports the changed attributes on individual
> instances is after_flush(). If you need the aggregate of all attributes
> that were changed over many fl
the after_commit() event is independent of any flush, so the last event where
the history API still reports the changed attributes on individual instances is
after_flush(). If you need the aggregate of all attributes that were changed
over many flushes within the span of a transaction, you'd p
Hi,
my question is how/if I can detect which attributes were changed when I get
the 'after_commit' event. (I think it isn't possible based on what I read in
the docs but I'd like to be sure.) If not, which other event could I use?
What I want to achieve: I want to update an external search index
Hi,
my question is how/if I can detect which attributes were changed when I get
the 'after_commit' event. (I think it isn't possible based on what I read in
the docs but I'd like to be sure.) If not, which other event could I use?
What I want to achieve: I want to update an external search index
