content_image/673192.jpg content_image/673196.jpg content_image/673193.jpg content_image/673194.jpg content_image/673195.jpg
<img src='content_image/673192.jpg'>

When set to 1  or ON , this variable enables batching of statements within the same transaction. To use this variable, autocommit  must first be disabled by setting it to 0  or OFF ; otherwise, setting transaction_allow_batching  has no effect. 

It is safe to use this variable with transactions that performs writes only, as having it enabled can lead to reads from the “before”  image. You should ensure that any pending transactions are committed (using an explicit COMMIT  if desired) before issuing a SELECT . 

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

This variable is currently supported for NDB Cluster only. 

## Important 

transaction_allow_batching  should not be used whenever there is the possibility that the effects of a given statement depend on the outcome of a previous statement within the same transaction. 

The system variables in the following list all relate to the ndbinfo  information database. 

• ndbinfo_database 

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

Shows the name used for the NDB  information database; the default is ndbinfo . This is a read-only variable whose value is determined at compile time. 

• ndbinfo_max_bytes 

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

Used in testing and debugging only. 

• ndbinfo_max_rows 

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

