Description: As I have no test case, only strong presomptions, I sent this to mys...@lists.mysql.com but got no feedback. I use MySQL-Max 4.0.1 with InnoDB tables with binary logging on. I see that the BEGIN and COMMIT statements that wrap my queries are not written to the binary log. I perfectly understand this if I have one server. But assume I have a master server, and a slave server that replicates the master. Let's say I distribute reads. Let's say I issue the following queries on the master (I use BEGIN and COMMIT for consistency) : BEGIN; UPDATE accounts set sum=sum-100 where num=10; UPDATE accounts set sum=sum+100 where num=12; # I don't work in a bank !! COMMIT; then only UPDATE accounts set sum=sum-100 where num=10; UPDATE accounts set sum=sum+100 where num=12; is written to the master's binary log, and then propagates to the slave. Assume that, while it is propagating I issue a reading query on the slave : SELECT sum from accounts where num in(10,12); Then, to my mind, this select might be treated AFTER the first update being processed by the slave, and BEFORE the second update being processed by the slave. Then I'll get not-consistent results. This would not happen if BEGIN and COMMIT had been written to the master's binary log. Am I misunderstanding something ? If this problem really exists, is it to be fixed ? Thanks anyway !

How-To-Repeat: This is not repeatable, it depends on the milliseconds I suppose

Fix:

Synopsis: <BEGIN/COMMIT statements not written to the binary log> Submitter-Id: <submitter ID> Originator: <BICHOT> Organization: <your organization> MySQL support: [none] Severity: [non-critical | serious | critical ] Priority: [low | medium | high ] Category: [mysqld] Class: [ sw-bug | doc-bug | change-request | support ] Release: mysql-4.0.1

Exectutable: [mysqld-nt] Environment: <machine description> System: <Win2000> Compiler: VC++ 6.0 Architecture: i586

To request this thread, e-mail bugs...@lists.mysql.com To unsubscribe, e-mail <bugs...@lists.mysql.com>