id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc
151	look into mixed replication etc.	geofft		"MySQL supports [http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html two major replication formats]: statement-based, where the query is logged and replayed, and row-based, where the changed data is logged and replayed. Statement-based is much older and presumed more stable, and the default in 5.x; [http://dev.mysql.com/doc/refman/5.1/en/replication-sbr-rbr.html row-based handles a couple of nondeterministic queries] that statement-based replication can't. MySQL 5.1.8 also introduced [http://dev.mysql.com/doc/refman/5.1/en/binary-log-mixed.html mixed-format logging], which uses statement-based replication where it can and row-based where necessary. 5.1.12 made mixed replication the default, until it was [http://bugs.mysql.com/bug.php?id=39812 reverted in 5.1.29 on the grounds that 5.1 should be compatible with 5.0]. We should decide on our own whether we want to use mixed replication (I think there's no compelling need to switch to row-based replication for everything). Among other obvious benefits, more reliable replication means that backups are more likely to match what you see on the primary.

Relatedly, MySQL used to permit users to set a session variable, [http://dev.mysql.com/doc/refman/5.1/en/server-options.html#option_mysqld_binlog-format `binlog_format`], to switch logging types for the duration of that session. However, this ability was [http://bugs.mysql.com/bug.php?id=39106 restricted to users with the SUPER privilege] (which has always been required for setting that as a _global_ variable), because someone claimed that DBAs might write code that required row-based replication and didn't want a mere user to be able to switch to statement-based replication and foil the DBA's plans. While I question the validity of such a possibility, we certainly don't have DBAs, so it might be worth locally reverting that patch so that users and applications have the option of switching to row-based replication if they prefer it. This would be especially important if we [ticket:150 go through autoinstalled apps to see what, if anything, wouldn't work properly statement-based replication]."	enhancement	closed	normal		sql	fixed