MySQL 5.0 - note
MySQL 5.0 - note
- Subject: MySQL 5.0 - note
- From: Kieran Kelleher <email@hidden>
- Date: Mon, 18 Feb 2008 16:53:44 -0500
| Any of you who use MySQL with InnoDB (you should be using InnoDB!), then note the following change in the upgrade notes. I would think you would want the whole transaction to be rolled back on timeout.........
Incompatible change: As of MySQL 5.0.13, InnoDB rolls back only the last statement on a transaction timeout. In MySQL 5.0.32, a new option, --innodb_rollback_on_timeout, causes InnoDB to abort and roll back the entire transaction if a transaction timeout occurs (the same behavior as in MySQL 4.1).
.... anyway, just an FYI (if I am reading this correctly) to those who don't want a partial editingContext.saveChanges() to ever happen in the event your WOA app server dies in the middle of a transaction.
Regards, Kieran |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden