Re: MySQL 5.0 - note
Re: MySQL 5.0 - note
- Subject: Re: MySQL 5.0 - note
- From: "Cheong Hee (Datasonic)" <email@hidden>
- Date: Tue, 19 Feb 2008 14:33:16 +0800
May be by default, you pay less, if you'd need to. MyISAM is cheaper..
Thanks Kieran for useful info, and thought by default MySQL should do so.
Is FrontBase do the same roll back if timeout?
Cheong Hee
Message: 13
Date: Tue, 19 Feb 2008 10:58:45 +1100
From: Lachlan Deck <email@hidden>
Subject: Re: MySQL 5.0 - note
To: WebObjects-Dev List <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden