MySQL Bugs: #74825: Incorrect description of MIXED-mode binlog

Bug #74825	Incorrect description of MIXED-mode binlog_format
Submitted:	13 Nov 2014 2:29	Modified:	10 Apr 2015 14:32
Reporter:	Brian Papantonio	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.7, 5.6, 5.5, 5.1	OS:	Any
Assigned to:	David Moss	CPU Architecture:	Any

Description:
On this page under section A.13.10:
http://dev.mysql.com/doc/refman/5.6/en/faqs-replication.html#qandaitem-A-13-1-10

it is stated: "For MIXED mode, row-based logging is preferred but replication switches automatically to statement-based logging under certain conditions".

Although the word "preferred" is arguably subjective, there are numerous other examples in the manual that state the opposite preference, such as this page:
http://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_binlog_f...

"When MIXED is specified, statement-based replication is used, except for cases where only row-based replication is guaranteed to lead to proper results."

And this page:
http://dev.mysql.com/doc/refman/5.6/en/binary-log-mixed.html

"When running in MIXED logging format, the server automatically switches from statement-based to row-based logging under the following conditions"

How to repeat:
--

Suggested fix:
Change the text to read: "For MIXED mode, statement-based logging is preferred but replication switches automatically to row-based logging under certain conditions"

Hello Brian Papantonio,

Thank you for the report.

Thanks,
Umesh

Thanks for your feedback Brian, I have fixed this in the FAQ now. The sentence reads:
For MIXED mode, statement-based logging is used by default but replication switches automatically to row-based logging under certain conditions, such as unsafe statements.