this has come up on occasion, but the attribute event system was originally written to suit the use case of the “backref” as well as for validation, so the python logic that fires it off is placed before the data is actually set. There is no logic for an “after” event within that scope. You can use regular Python idioms for this kind of thing, such as overriding __setattr__() on classes.
On Dec 28, 2013, at 8:43 AM, Alexey Vihorev <viho...@gmail.com> wrote: > Hi all! > The line event.listen(MyClass.my_attr, 'set', my_listener_method) allows me > to react on an attribute being set. However, this event is fired BEFORE the > attribute is actually set. And my app’s logic requires me to catch the event > AFTER the attribute is set (Using MVVM pattern, I need to notify VM that M > has actually changed). How should I go about that? Thanks! > > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email tosqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
