Innodb tables with 1 MyISAM table

[Mike Rogers]

Hi All,

I know that mixing MyISAM and Innodb tables in a single DB is do-able and that MyISAM lacks foreign key constraints and transactional capabilities but I am wondering if anyone can give me some comfort that this mix will work well in a very busy production environment?

We have one particular INNODB table which experiences very large numbers of deletes/updates/inserts. The table locking for AUTO-INC columns issue (which is solved in version 5.1 but not in 5.0) is biting me and deadlocks and horrible lock waits are common due to this. A possible solution is to have the guilty table be replaced with a MyISAM table which would eliminate the problem (I think).

Has anyone out there used mixed tables successfully in high write/delete/update systems?

Thanks

Mike