Re: [Sqlalchemy-tickets] [sqlalchemy] #2684: mutually dependent object cycle, detection w/ m2o/o2m without the backref

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

#2684: mutually dependent object cycle, detection w/ m2o/o2m without the backref
-----------------------------------+-------------------------------
      Reporter:  vsevolod_fedorov  |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  medium            |  Milestone:  0.8.xx
     Component:  orm               |   Severity:  major - 1-3 hours
    Resolution:  wontfix           |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+-------------------------------
Changes (by zzzeek):

 * status:  new => closed
 * resolution:   => wontfix
 * status_field:  in queue => completed/closed


Comment:

 I think im going to close this because a mutually dependent FK situation
 will need post_update in the vast majority of cases anyway, and to try to
 get it to work around the case when there aren't actually any
 insert/delete cycles is quite difficult - it would be code that almost
 never gets used since post_update would normally be on anyway.

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