I was really surprised too when I looked over the upgrade notes
before upgrading some slaves to 5.0..... very strange decision.
Ah well .... missing stuff like this is the risk we take by not being
paying "MySQL Enterprise Customers" :-(
So basically one just needs to just add a line to /etc/my.cnf with
innodb_rollback_on_timeout
Regards, Kieran
On Feb 18, 2008, at 6:58 PM, Lachlan Deck wrote:
On 19/02/2008, at 8:53 AM, Kieran Kelleher wrote:
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.
Thanks Kieren. I can't understand why InnoDB would include MyISAM
behaviour by default :-/
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
