content_image/863517.jpg content_image/863516.jpg
## 17.5.1.35 Replication and Transactions 

Mixing transactional and nontransactional statements within the same transaction.  In general, you should avoid transactions that update both transactional and nontransactional tables in a replication environment. You should also avoid using any statement that accesses both transactional (or temporary) and nontransactional tables and writes to any of them. 

The server uses these rules for binary logging: 

•If the initial statements in a transaction are nontransactional, they are written to the binary log immediately. The remaining statements in the transaction are cached and not written to the binary log until the transaction is committed. (If the transaction is rolled back, the cached statements are written to the binary log only if they make nontransactional changes that cannot be rolled back. Otherwise, they are discarded.) 

•For statement-based logging, logging of nontransactional statements is affected by the binlog_direct_non_transactional_updates  system variable. When this variable is OFF (the default), logging is as just described. When this variable is ON , logging occurs immediately for nontransactional statements occurring anywhere in the transaction (not just initial nontransactional statements). Other statements are kept in the transaction cache and logged when the transaction commits. binlog_direct_non_transactional_updates  has no effect for row-format or mixed- format binary logging. 

## Transactional, nontransactional, and mixed statements. 

To apply those rules, the server considers a statement nontransactional if it changes only nontransactional tables, and transactional if it changes only transactional tables. A statement that references both nontransactional and transactional tables and updates any  of the tables involved is considered a “mixed” statement. Mixed statements, like transactional statements, are cached and logged when the transaction commits. 

A mixed statement that updates a transactional table is considered unsafe if the statement also performs either of the following actions: 

•Updates or reads a temporary table 

•Reads a nontransactional table and the transaction isolation level is less than REPEATABLE_READ 

A mixed statement following the update of a transactional table within a transaction is considered unsafe if it performs either of the following actions: 

•Updates any table and reads from any temporary table 

•Updates a nontransactional table and binlog_direct_non_transactional_updates  is OFF 

For more information, see Section 17.2.1.3, “Determination of Safe and Unsafe Statements in Binary Logging” . 

<img src='content_image/863517.jpg'>

<img src='content_image/863516.jpg'>

## Note 

A mixed statement is unrelated to mixed binary logging format. 

In situations where transactions mix updates to transactional and nontransactional tables, the order of statements in the binary log is correct, and all needed statements are written to the binary log even in case of a ROLLBACK . However, when a second connection updates the nontransactional table before the first connection transaction is complete, statements can be logged out of order because the second connection update is written immediately after it is performed, regardless of the state of the transaction being performed by the first connection. 

