[ZODB-Dev] ZODB 3.2.4 ConnectionStateError

[Syver Enstad]

"Tim Peters" <tim at zope.com> writes:

> > The reason I am concerned about this is that I have a relatively large
> > web based system using ZODB and I don't want the entire web server to go
> > down just because one of the web pages has a bug in it. Maybe one should
> > always do connection.getTransaction().abort() before closing the
> > connection?
> 
> Some people would say that
> Zope is also a relatively large web based system using ZODB that doesn't
> want to go down just because a web page has a bug in it, and that's what it
> does <wink>.  All the examples above still *appear* to allow the whole app
> to go down if a conflict error occurs (because there's no code in them to
> catch, deal with, and suppress conflict errors).

Isn't transaction.abort() enough to deal with a conflict error?