Hi Andrei,
Ok to push from me.
Andrei Elkin, 04.02.2008 15:37:
...
> ChangeSet@stripped, 2008-02-04 16:37:41+02:00, aelkin@stripped +2 -0
> Bug#33329 extraneous ROLLBACK in binlog on connection
> does not use trans tables
>
> There had been two issues.
> Rollback statement was recorded in binlog even though a multi-update
> had not modified any non-transactional table.
> The reason for this artifact was a false initial value of
> multi_update::transactional_tables.
> Yet another artifact that explained on the bug page is that
> `ha_autocommit_or_rollback' works differently depending on whether
> a transaction engine has been compiled in.
>
> Fixed: with setting multi_update::transactional_tables to zero at initialization
> time. Multi-update on non-trans table won't cause ROLLBACK in binlog with
> either compilation option.
>
> The 2nd mentioned artifact comprises a self-standing issue (to be reported
> separately).
Regards
Ingo
--
Ingo Strüwing, Senior Software Developer
MySQL GmbH, Dachauer Str. 37, D-80335 München
Geschäftsführer: Kaj Arnö - HRB München 162140