RE: [Zope-dev] Serious bug with gadfly transactions?
If you use relational databases with Zope, please read: In the context of Database Adapters, Zope 2 introduces two new things: (a) concurrency (b) a different (better, faster, cheaper.. um, well still free) approach to transactions EACH Database Adapter has to be modified so that it addresses (a) above. This will be done according to the Levels detailed in an earlier post. To briefly recap: o Level 1 DA -- you must run Zope2 in single-threaded mode o Level 2 DA -- "thunked.." transactions are serialized inside the DA code o Level 3 DA -- fully threaded A different and largely unrelated issue is how the DA interacts with Zope's transaction machinery (i.e., (b) above). With the exception of a Sybase DA we are working internally for a consulting customer we have not made any progress (internally) on this. This will cause the behavior Martijn describes below. A DA can be Level 3, high-speed, long-range, low-drag and still not be integrated with the new transaction machinery. Conversely, a DA can be integrated into the new transaction machinery and require Zope be run in single threaded mode. I _guarantee_ that today, we will make a Database Adapater status page available on the Zope site. --Rob
-----Original Message----- From: Martijn Pieters [mailto:mj@antraciet.nl] Sent: Wednesday, July 28, 1999 7:36 AM To: Zope Development Subject: [Zope-dev] Serious bug with gadfly transactions?
I'm looking for confirmation on this:
In Zope 2.0b1 (and the latest CVS):
- When using a gadfly database, nothing is committed, ever. When shutting down Zope, all transactions to gadfly are aborted, and all data is gone.
- When doing multiple SQL update/insert/create calls, and making an error in any but the first call leaves any previous call in the DB, they are not rolled back. So, when, in one request, you do an insert and an update, and the update raises an error, the insert is not rolled back.
Does anyone else see this?
-- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://www.zope.org/mailman/listinfo/zope-dev
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For non-developer, user-level issues, zope@zope.org, http://www.zope.org/mailman/listinfo/zope )
In article <613145F79272D211914B0020AFF6401915C64A@gandalf.digicool.com> , Rob Page <rob.page@digicool.com> writes
In Zope 2.0b1 (and the latest CVS):
- When using a gadfly database, nothing is committed, ever. When shutting down Zope, all transactions to gadfly are aborted, and all data is gone.
This was the same problem I was having with ODBC that I reported a couple of days ago. ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz
participants (2)
-
Graham Chiu -
Rob Page