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:  invalid           |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+------------------------------------

Comment (by zzzeek):

 Replying to [comment:8 schlamar]:
 > You should even consider if autoflush=False as default doesn't fit
 better to your "no magic" policy.

 that's how it was for years.  autoflush being on has solved a lot of
 problems.   I'd ask that you consider this project has been going for
 eight years and has evolved tremendously.  At this point, not a lot is by
 accident anymore.

 > The behavior above is really unexpected (and I couldn't find any clue
 about such an issue in documentation) and I found similar issues regarding
 autoflush across the net, e.g. http://lists.okfn.org/pipermail/ckan-
 dev/2011-January/000189.html

 there were many issues with autoflush being turned off too.

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