• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: MySQL 5.0 - note
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MySQL 5.0 - note


  • Subject: Re: MySQL 5.0 - note
  • From: Lachlan Deck <email@hidden>
  • Date: Tue, 19 Feb 2008 10:58:45 +1100

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


  • Follow-Ups:
    • Re: MySQL 5.0 - note
      • From: Kieran Kelleher <email@hidden>
References: 
 >MySQL 5.0 - note (From: Kieran Kelleher <email@hidden>)

  • Prev by Date: MySQL 5.0 - note
  • Next by Date: Re: MySQL 5.0 - note
  • Previous by thread: MySQL 5.0 - note
  • Next by thread: Re: MySQL 5.0 - note
  • Index(es):
    • Date
    • Thread