Le dimanche 14 février 2010 à 19:58 +0100, Wichert Akkerman a écrit : > On 2/14/10 19:54 , Antoine Pitrou wrote: > > Le dimanche 14 février 2010 à 19:45 +0100, Wichert Akkerman a écrit : > >> > >> That is by design: zope.sqlalchemy (which is really the thing you are > >> complaining about) forces you to commit the entire transaction. This is > >> required to coordinate transactions between multiple participants in a > >> transaction, prevent one of them from getting out of sync. > > > > I understand this is by design, but better again would have been a flag > > to disable it. > > I have never seen a request for such a flag before, which makes me > suspect it is not a widely requested feature. You are more than welcome > to contribute such a flag to zope.sqlalchemy though.
Well the primary use for it is that session.commit() doesn't expunge the session, while transaction.commit() does. So the real fix, or improvement, would be to change or at least make configurable transaction.commit()'s behaviour. > If you are trying to put blame anywhere do it in the right place: the > 'transaction' package does not do this. The SQLAlchemy transaction glue > in the zope.sqlalchemy package does. Oh, sorry. That doesn't really change my point, though, since we are talking about use of "transaction" in an SQLAlchemy context. Regards Antoine. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. 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.
