Yah, that's a surprise to me too. I usually .flush() anyway (it's just good hygiene :), but never knew that session.commit() implied session.flush()
On 12/26/07, Denis S. Otkidach <[EMAIL PROTECTED]> wrote: > > > On Dec 26, 2007 6:29 PM, Michael Bayer <[EMAIL PROTECTED]> wrote: > > yet another scenario, you want to use transactions that are > > independent of session flushes. To accomplish this, use engine- or > > connection-level transactions, as described in the second half of > > http://www.sqlalchemy.org/docs/04/session.html#unitofwork_sql . in > > this case you control the transactions independently of any session > > behavior, yet the session still participates (at your choosing) in the > > overall transaction. > > > > Hope this helps. > > Sure, this is what I needed. Thanks! I believe SA documentation should > explicitly state that session.commit() always flushes all modified > objects independent on autoflush option. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
