[ZODB-Dev] RE: [Zope-Annce] ZODB 3.2.4 release candidate 1released

[Florent Guillaume]

In article <20040909023157.9ADA33B8038 at smtp.zope.com> you write:
> [Tim, on magically getting a new transaction when commit() fails]
> > But that's not how it works, and God only knows what would break if it got
> > changed.  It works that way in 3.3 too, although there you truly (not just
> > "effectively") get a new transaction after a commit() attempt.
> 
> So what do people think about this for 3.3?  It's still in beta, so it's
> still *possible* to change 3.3's default TransactionManager to one that
> doesn't magically dump you into a new transaction if the current
> transaction's commit() fails.  People who know far more about Zope than I do
> (like Chris and Shane) consistently say they want that.  I know a number of
> ZODB tests would fail, but I don't care about that -- they're not *relying*
> on the current behavior, they're testing to make sure it stays broken
> <wink>.

Oh yes +1 please. It's part of the "explicit is better than implicit",
starting a new transaction when commit() fails is too much magic, better
have something high-level (like ZPublisher) be responsible for doing it
explicitely.

Florent

-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 71 59  http://nuxeo.com  mailto:fg at nuxeo.com