Re: MySQL: InnoDB vs MyISAM or InnoDB + MyISAM
Re: MySQL: InnoDB vs MyISAM or InnoDB + MyISAM
- Subject: Re: MySQL: InnoDB vs MyISAM or InnoDB + MyISAM
- From: David LeBer <email@hidden>
- Date: Wed, 02 May 2012 11:54:47 -0400
Bah, the world as we know it sucks.
Seeing the end of the world as we *don't* know it, now there is something I'd pay big money to see.
D
PS: I concur, use InnoDB everywhere.
--
David LeBer
Codeferous Software
On 2012-05-02, at 11:45 AM, Kieran Kelleher wrote:
> Big problems. As has been said before, MyISAM will not rollback... Thus every failed editingContext.saveChanges() will result in loss of data integrity and end of the world as we know it.
>
>
> Save the World: Use InnoDB only when using MySQL
>
> Regards Kieran
> ___________________________
> Sent from my iPad.
>
>
> On May 2, 2012, at 10:46 AM, Ron X <email@hidden> wrote:
>
>> Did anybody do chain like this - InnoDB (some tables) + MyISAM (other tables)?
>> And what problems I will get when will use this sheme?
>> Thanx.
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
_______________________________________________
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