Re: MyISAM and Webobjects
Re: MyISAM and Webobjects
- Subject: Re: MyISAM and Webobjects
- From: Kieran Kelleher <email@hidden>
- Date: Tue, 30 Oct 2012 10:03:02 -0400
So, it might be stating the obvious, but the primary consequence of using a non-transactional database such as MyISAM with WebObjects is that a failed EOEditingContext.saveChanges() will not be rolled back in the database which causes the unsaved EC changes to be actually *partially* saved resulting in inconsistent data, orphan records, relationships pointing to objects that don't exist, etc. and the most common error thrown by your app will become EOObjectNotAvailableException .... basically chaos and corrupt useless data because you shot yourself in the foot over and over :)
On Oct 29, 2012, at 7:23 PM, Ramsey Gurley <email@hidden> wrote:
> MyISAM is not ACID. WO was designed around the concept of ACID transactions with highly consistent data.
>
> http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
>
> Ramsey
>
> On Oct 29, 2012, at 3:09 PM, Gino Pacitti wrote:
>
>> Hi list
>>
>> I read in the wiki a reference to WO not using MyISAM in tables but no explanation why - any pointers to an explanation.
>>
>> Gino
>> _______________________________________________
>> 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