Re: [Sqlalchemy-tickets] [sqlalchemy] #2809: Strange effect with association proxy and event listener

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

#2809: Strange effect with association proxy and event listener
-----------------------------------+------------------------------------
      Reporter:  schlamar          |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  medium            |  Milestone:  0.8.xx
     Component:  (none)            |   Severity:  no triage selected yet
    Resolution:  worksforme        |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+------------------------------------
Changes (by zzzeek):

 * status:  new => closed
 * resolution:   => worksforme
 * status_field:  awaiting triage => completed/closed


Comment:

 the traceback has "autoflush" inside of it, which occurs each time the
 Session needs to go to the database to get some data.   In this traceback,
 as append() is called, the collection to which it is appending is
 unloaded, so has to be loaded first, triggering autoflush.

 Issues where autoflush gets in the way in some object mutation scenarios
 are common.  Use the
 [http://docs.sqlalchemy.org/en/rel_0_8/orm/session.html?highlight=no_autoflush#sqlalchemy.orm.session.Session.no_autoflush
 no_autoflush] context manager to temporarily turn it off.

 also since there's no specific "bug" defined here (no test case) this is
 more of a mailing list issue for the moment, can we please move it over
 there?  thanks.

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