Re: Change from InnoDB to MyISAM storage engine
If you switch to MyISAM as a workaround for the InnoDB FK re-use bug, you lose all transactional control, all FKs, and much performance.
Granted, there are other InnoDB bugs too, but in your shoes, before abandoning transactional logic I'd investigate these alternatives ...
(i) find out if Percona XtraDB (a child of InnoDB) has fixed this InnoDB bug, and if it has, switch to MariaDB and XtraDB
(ii) make sure all FKs have active On Delete On Update clauses
(iii) add code that works around this InnoDB bug
(iv) replace Fks with application code that enforces relational integrity
Subject
Views
Written By
Posted
2275
March 29, 2016 04:01AM
Re: Change from InnoDB to MyISAM storage engine
1418
March 29, 2016 09:20AM
1403
March 30, 2016 07:40AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.