Re: [Sqlalchemy-tickets] [sqlalchemy] #2789: possible approach to the "append/set/clear/remove" attribute event issue

[sqlalchemy <mi...@zz...>]

#2789: possible approach to the "append/set/clear/remove" attribute event issue
-----------------------------------+-------------------------------
      Reporter:  zzzeek            |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  high              |  Milestone:  0.9.0
     Component:  orm               |   Severity:  major - 1-3 hours
    Resolution:  fixed             |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+-------------------------------
Changes (by zzzeek):

 * status:  new => closed
 * resolution:   => fixed
 * status_field:  not decided upon => completed/closed


Comment:

 I made much more of a change here, including coming up with a more
 informative event token without sacrificing performance, and also moving
 all the "halt event" logic into backref handlers, where it can be managed
 more effectively and also should save on method call overhead.  r550141b.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2789#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python