Quote:
Originally Posted by borked
take this simple setup as an example:
tables:
models
models_films
films
models_films links models to the films they are in.
You want to delete a model from the models table....
In INNODB, you have to delete the model entry in models table plus all the entries in models_films that contains the model_id. With all the re-indexing that mysql does behind the scenes on data delete
In InnoDB, you simply delete the model, and if the relationships are correctly set, all the entries in models_films will auto-delete too. When you've got like 10 tables that are relationally-linked, this simple shit is priceless....
Not to mention rolling back on a transaction.
So, no, myisam can suck both my nuts ;)
Well written series Varius  |
Both tables have their uses; neither one sucks any nuts
For example, full-text indexes are not possible in InnoDB yet, but they are in INNODB.
INNODB is for high-read volume with little to no update volume (update,insert,delete).
InnoDB is for high-update volume, as table vs. row-level locking make a huge difference.