Re: [Sqlalchemy-tickets] [sqlalchemy] #1672: supply "detect" option for passive_updates

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

#1672: supply "detect" option for passive_updates
-----------------------------------+-------------------------------
      Reporter:  zzzeek            |      Owner:  zzzeek
          Type:  enhancement       |     Status:  closed
      Priority:  medium            |  Milestone:  0.x.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:  awaiting triage => completed/closed


Comment:

 this is really not needed at all, mutable primary keys are already a rare
 edge case, and then the cases where "passive_updates=False" actually
 creates a problem on an FK database is very rare, essentially there's one
 test in test_naturalpks that illustrates this.    there's not an easy way
 to detect this condition in any case as on MySQL is per-table.   not
 really worth it.

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