Re: Need suggestion: Using InnoDB and MyISAM together

[Walter Heck]

In general, if you are relying on transactions, you should consider using innodb unless you have a good reason not to. Changing a storage engine on a table is very simple, so I don't quite understand your motivation to only do it for half your tables. Could you explain that a bit more?

A good reason to stick to InnoDB as much as possible when using an app that uses transactions: Right now it might seem easier to only convert what is needed. However, if you leave half your tables on MyISAM and a few years down the line the app needs expanding, the dev in question might not look at the engine or just look at the engine of one or two tables. Then, assuming all is InnoDB, you might end up with a _big_ mess :)

my 2 cents :)

Walter