Bug #77250 binlog_format and the query log
Submitted: 5 Jun 2015 3:29 Modified: 14 Aug 2015 21:51
Reporter: Hongyu Qiao Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: Christine Cole CPU Architecture:Any
Tags: documant bug

[5 Jun 2015 3:29] Hongyu Qiao
Description:
MySQL 5.6 Reference Manual :: 5 MySQL Server Administration :: 5.2 MySQL Server Logs :: 5.2.3 The General Query Log

The third paragraph:

When using statement-based logging all statements are written to the query log, but when using row-based logging, updates are sent as row changes rather than SQL statements, and thus these statements are never written to the query log when  is ROW. A given update also might not be written to the query log when this variable is set to MIXED, depending on the statement used. See Section 17.1.2.1, “Advantages and Disadvantages of Statement-Based and Row-Based Replication”, for more information.

Did binlog_format influence the content of the general query log?

How to repeat:
To see MySQL 5.6 Reference Manual :: 5 MySQL Server Administration :: 5.2 MySQL Server Logs :: 5.2.3 The General Query Log
[17 Jun 2015 12:40] MySQL Verification Team
Thanks for the report

kind regards
Bogdan Kecman
[14 Aug 2015 21:51] Christine Cole
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.