• 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: Kieran Kelleher <email@hidden>
  • Date: Tue, 19 Feb 2008 07:46:27 -0500

Cheong,

I use this week's latest (5.0.51a) .... the original message to the list was inspired by reading the upgrade notes which say the last *statement* is rolled back in the event of a timeout by default unless you use the option given.

InnoDB is free. My reference to paying was that if you were a paying customer, then you would not have to worry about reading details in the upgrade notes since the MySQL Advisors would configure your my.cnf for you!

Cheong, MyISAM is not transactional ...... if using it, you will surely end up with messed up database and many orphan foreign keys!

Kieran


On Feb 19, 2008, at 5:16 AM, Cheong Hee (Datasonic) wrote:

Hi Andrew

I could be wrong. Thought Kieren meant the new version:32 rolls back the entire transaction(s) if a timeout occurs for the last transaction. ...and therefore saveChanges will ensure all or none of the transactions will be committed into database. So no partial save. I am using version 26, and did not notice the issue. Could do a test later of the night.


"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)."

Terribly sorry if I got it the other way around.   Thanks.

Cheers

Cheong Hee


----- Original Message ----- From: "Andrew Lindesay" <email@hidden>
To: "Cheong Hee (Datasonic)" <email@hidden>
Cc: <email@hidden>
Sent: Tuesday, February 19, 2008 3:00 PM
Subject: Re: MySQL 5.0 - note



Hello Cheong;

The "typical" transaction behaviour would be for either all of a transaction to be stored corrected in the database server or none of the transaction would be stored. Kieren is describing a situation where some of a transaction is stored and some is not stored so you can't be sure what has been stored and what has not. Doesn't sound like a happy situation.

cheers.

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?

___ Andrew Lindesay technology : www.lindesay.co.nz business : www.silvereye.co.nz




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com


This email sent to email@hidden

_______________________________________________ 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: "Cheong Hee (Datasonic)" <email@hidden>
References: 
 >Re: MySQL 5.0 - note (From: "Cheong Hee (Datasonic)" <email@hidden>)
 >Re: MySQL 5.0 - note (From: Andrew Lindesay <email@hidden>)
 >Re: MySQL 5.0 - note (From: "Cheong Hee (Datasonic)" <email@hidden>)

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