Alfranio Correia wrote:
> Hi all,
>
> updates:
>
> Theres is a final patch, at least from my point of view :), available at
> http://lists.mysql.com/commits/74255
Will check.
[snip]
> 5) M...: where M is either N T or T N.
>
> This case is handled as 3 or 4.
The notion that a mixed statement is either NT or TN implies an ordering within
the statement. That is actually not relevant, since the granule of execution is
a statement from the point of the scheduler.
[snip]
> IMPLEMENTATION DETAILS
> ----------------------
>
> There are two caches: one for transactional changes (trx-cache) and
> another one
> for non-transactional changes (nontrx-cache). The trx-cache is flushed and
> truncated before committing or rolling back a transaction. The
> nontrx-cache is
> flushed and truncated before finishing a statement. For the 5 cases
> described
> above, these caches are used as follows:
>
> 1) B T...T C/R: all the statements are transactional.
>
> In STMT, ROW and MIXED modes, statements or changes are copied to the
> trx-cache
> and flushed to the binary log upon committing a transaction or just ignored
> upon rolling a transaction back.
>
> 2) B N...N C/R: all the statements are non-transactional.
>
> In STMT, the statements are copied to the trx-cache and flushed to the
> binary
> log upon committing or rolling back a transaction. In ROW and MIXED mode,
> changes
do you mean rows?
> are copied to the nontrx-cache and flushed to the binary log as
> soon as
> each statement is completed.
>
Best wishes,
Mats Kindahl
--
Mats Kindahl
Senior Software Engineer
Database Technology Group
Sun Microsystems
