[Zope-DB] Problems with transaction management and many database adapters

Dieter Maurer dieter at handshake.de
Wed Feb 4 16:10:19 EST 2004

Marco Bizzarri wrote at 2004-2-3 16:29 +0100:
> ...
>The problem is in the paflow.js javascript file, which is in the 
>standard_html_header. The browser, behind the scene, after getting the 
>index_html, tries to get the paflow.js. However, since this is not 
>present, it raises a resource not found error, and sends back to the 
>browser an error page (which is not shown to the user, since this error 
>is silently captured by the browser). The error produces a 
>standard_error_message page, which, by default, includes the 
>standard_html_header, which calls the menu_html which calls the SQL 
>Method (oh gawd!). Here is either the feature or the strange behaviour: 
>this is the second transaction which is not closed (no commit/rollback 
>at the end). Is this a known behaviour?

It is known:

  Transactions modified during error handling are not properly

There has been a long discussion between Toby and me on "zope-dev".

  Toby convinced me that the abort should happen after
  error handling (and not before, as does the usual Zope code).

I fear, the problem is still present in all official Zope versions.


More information about the Zope-DB mailing list