MySQL Bugs: #71012: Condition/Action table on "Mixed Binary Logging Format" seems wrong / unclear

Bug #71012	Condition/Action table on "Mixed Binary Logging Format" seems wrong / unclear
Submitted:	26 Nov 2013 13:05	Modified:	29 Jan 2014 13:39
Reporter:	Paul Keenan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S4 (Feature request)
Version:	5.5+	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
I've been reading the "Mixed Binary Logging Format" page (http://dev.mysql.com/doc/refman/5.6/en/binary-log-mixed.html) and there seems to be two problems with the page :

(1) In the final table which explains which type of replication is used for which circumstances, there is a row with the following conditions :

   Type          = Safe
   binlog_format = MIXED
   SLC           = Yes
   RLC           = Yes

The table says that for these conditions, the action is logged as ROW.  My understanding is that the whole point of mixed-mode replication is that STATEMENT is preferred when the logging could be done either way and the statement is safe.  Can you explain ?

"Row-injection" is mentioned as a type of operation 

How to repeat:
Visit http://dev.mysql.com/doc/refman/5.6/en/binary-log-mixed.html

Suggested fix:
Verify contents condition/action table for case when
   Type          = Safe
   binlog_format = MIXED
   SLC           = Yes
   RLC           = Yes
and amend "logged as" column if appropriate.

Explain what "row injection" and "binary injected" mean on the page or use replacement terms which are already explained.

Sorry, hit "submit" prematurely.

(2) "Row-injection" is mentioned as a type of operation in the Condition/Action table, and seems to be referred to as "binary-injected" in the text preceding it 

    "In MySQL 5.6, whether a statement is to be logged and the logging mode to be used is determined according to the type of statement (safe, unsafe, or binary injected)"

The terms "Row-injection" and "binary-injected" are not explained elsewhere as far as I can see, and a Google search wasn't much help as it tended to lead to discussion on SQL injection attacks.

Can you either define the terms, provide a link to another page where they are defined or use different terms which the reader is more likely to be aware off.

Cheers,
Paul

Replication -> mine.

It's not unreasonable to expect terms to be defined. :)

Set status to Verified. I will try to fix this in the next day or two.

cheers

jon.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Fixed in mysqldoc rev 37550, Closed.