The one exception to this I can think of is read-only data, for really large data sets where the speed of reads is paramount. But you'd only go for such a thing as a last resort, to avoid the premature optimisation syndrome.
On 30/10/2012, at 10:23 AM, Ramsey Gurley <rgur...@smarthealth.com> 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 (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com >> >> This email sent to rgur...@smarthealth.com > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/lachlan.deck%40gmail.com > > This email sent to lachlan.d...@gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
