Link Details

> REMEMBER! It's OK to mix table types in the same database! In fact it's recommended and frequently required.

Not a good idea.

From MySQL manual:

You can combine transaction-safe and non-transaction-safe tables in the same statements to get the best of both worlds. However, although MySQL supports several transaction-safe storage engines, for best results, you should not mix different storage engines within a transaction with autocommit disabled.

Like i said in the article.. you need both if you're going to have a log table and an articles table with full-text searching.. just be careful when you're running a join query on both which in the real world happens once in a blue moon. Look around the web and you fill find tons of sites who utilize both tables and are able to enjoy both benefits.

> Not a good idea.

Hmm... why not?

I think the original author understood the problems with transactional (isolation levels etc) and constraint handling differences between myisam and innodb, but didn't warn about them in the article. Personally I think innodb should be always preferred over myisam and indexing is better done with an indexing server.