On 3/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I'm in the planning stage of what will hopefully become my first non- > trivial web app. I'm trying to minimize future pain resulting from > poor planning, and have been reading up on DB trivia. > > If I use MySQL, how do I choose between MyISAM and InnoDB? What are > the trade-offs? It seems InnoDB is the way to go if I want to handle > rollbacks and such, but MyISAM may produce considerably shorter query > times. Is this true?
If you are going to use MySQL and have an application where the ratio of writes to reads is quite high, then InnoDB is a perfect solution because it does row-level locking instead of table-level locking (or so I've been lead to believe), a critical factor when doing lots of inserts and updates. Hope that helps. -- Chris Hartjes My motto for 2007: "Just build it, damnit!" rallyhat.com - digital photo scavenger hunt @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
