News for hackers. Stuff that matters.
Re:The MySQL MyISAM and InnoDB engines and a grocery checkout by idlewords on Tuesday October 13, 2009 @02:01PM (#879645)
I don't agree. MyISAM tables are easy to trash, and the table locking on update can bite you. There's no real disadvantage to using InnoDB other than having to learn to tune it a litte bit, and your data will be much safer.
Re:The MySQL MyISAM and InnoDB engines and a grocery checkout by chrisbolt on Tuesday October 13, 2009 @02:11PM (#879679)
Define 'easy to trash'. I've been using MyISAM without problems for years now.
Re:The MySQL MyISAM and InnoDB engines and a grocery checkout by spudlyo on Tuesday October 13, 2009 @05:19PM (#880112)
MyISAM is like the ext2 filesystem. You crash and you end up spending a long time doing an fsck, where you have to verify the consistency by walking all the data structures. InnoDB is more like ext3, where you can make things consistent by replaying the changes in the journal. Doing repair on a large MyISAM table can take hours and hours.
Re:The MySQL MyISAM and InnoDB engines and a grocery checkout by acl on Tuesday October 13, 2009 @02:19PM (#879706)
I'm curious about this too -- I've used MyISAM for many projects without a problem.
Re:The MySQL MyISAM and InnoDB engines and a grocery checkout by idlewords on Tuesday October 13, 2009 @02:52PM (#879776)
The two ways I've experienced:

1. Yank power cord while db writes are happening.

2. Grow the tables over a couple of GB in size.

Re:The MySQL MyISAM and InnoDB engines and a grocery checkout by Freaky on Tuesday October 13, 2009 @04:30PM (#880007)
The additional storage cost of InnoDB can be quite significant if you have a lot of data. We have about 4 billion rows in MyISAM, we simply wouldn't have space to do that with InnoDB.

Hopefully compressed tables will improve matters.