Login | Register
My pages Projects Community openCollabNet

Discussions > issues > [Issue 32] mysql 3 transactions

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Hide all messages in topic

All messages in topic

[Issue 32] mysql 3 transactions

Reply

Author jjneely
Full name Jack Neely
Date 2005-05-10 16:10:51 PDT
Message MySQL 3 not supporting rollbacks
Content-type: text/plain; charset=UTF-8

http://current.tigri​s.org/issues/show_bu​g.cgi?id=32



User jjneely changed the following:

                What |Old value |New value
====================​====================​====================​====================​
                 Summary|MySQL 3not supporting
MyS|mysql 3 transactions
MySQ
                        |QL 3 not supporting rollba|L 3 not supporting rollbac
                        |cks |ks
--------------------​--------------------​--------------------​--------------------​




------- Additional comments from jjneely at tigris dot org Tue May 10 16:10:51 -0700 2005 -------
I think the right way to fix this is to have the specific DB objects somehow
export the standard DB API 2.0 exceptions. However I've a patch that just
leaves nasty log entries when rollback() creates an exception.
Messages per page: