MySQL Bugs: #55760: Inconsistency of manual and behavior for binlog_direct_non_transactional

Bug #55760	Inconsistency of manual and behavior for binlog_direct_non_transactional_udpates
Submitted:	5 Aug 2010 6:24	Modified:	5 Aug 2010 9:34
Reporter:	Zhenxing He	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
In the manual for option binlog_direct_non_transactional_update, it states:

.... This variable has no effect when the binary log format is ROW or MIXED.

The behavior is that the option binlog_direct_non_transactional_updates will take effect for both STATEMENT mode and MIXED mode if the binlog format for current statement is STATEMENT. And the option will have no effect for ROW format (either ROW mode or format is ROW in MIXED mode).

Please update the documentation of the option and make it coincide with the behavior. 

How to repeat:
Check 

http://dev.mysql.com/doc/refman/5.1/en/replication-options-binary-log.html#sysvar_binlog_d...

Suggested fix:
Fix the manual

Thanks for the clarification. Corrected lead (for Docs bugs, this should be Stefan).

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.