Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.
- Create BookmarkCreate Bookmark
- Create Note or TagCreate Note or Tag
- DownloadDownload
- PrintPrint
Replication and Concurrency > Mixing Transactional and Nontransactional Tables
Mixing Transactional and Nontransactional Tables
It is important not to mix transactional and nontransactional tables in the same transaction.[9] Once you make changes to a nontransactional table, you cannot roll them back, so if the transaction is aborted or rolled back, your data can become inconsistent.
Warning
The same issue occurs when mixing transactional tables using different engines in the same transaction. If engines have different transaction isolation levels or different rules for statements that cause implicit commits, you can end up with problems similar to those described for mixing transactional and nontransactional tables.
This can happen even when using a single MySQL server, but in replicated environments things sometimes get even worse. So I’m including this section in the part about replication, even though it contains lessons for nonreplicated environments as well.
