Bug #66746 Invalid values for constant in documentation of Bin Log Event type
Submitted: 9 Sep 2012 20:52 Modified: 5 Oct 2012 11:09
Reporter: Julien Duponchelle Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jan Kneschke CPU Architecture:Any

[9 Sep 2012 20:52] Julien Duponchelle
Description:
In documentation for bin log event type (http://dev.mysql.com/doc/internals/en/binlog-event-type.html) you see that (values are hexadecimal):
17 DELETE_ROWS_EVENT
18 UPDATE_ROWS_EVENT
19 WRITE_ROWS_EVENT

But in sql/log_event.h you have this (values are integer):
/*
These event numbers are used from 5.1.16 and forward
*/
WRITE_ROWS_EVENT = 23,
UPDATE_ROWS_EVENT = 24,
DELETE_ROWS_EVENT = 25,

How to repeat:
Go to http://dev.mysql.com/doc/internals/en/binlog-event-type.html

Suggested fix:
Fix the documentation by using the correct values:
17 WRITE_ROWS_EVENT
18 UPDATE_ROWS_EVENT
19 DELETE_ROWS_EVENT
[10 Sep 2012 15:28] MySQL Verification Team
Thank you for the bug report.

mysql 5.5 >select hex(23);
+---------+
| hex(23) |
+---------+
| 17      |
+---------+
1 row in set (0.03 sec)

mysql 5.5 >select hex(24);
+---------+
| hex(24) |
+---------+
| 18      |
+---------+
1 row in set (0.00 sec)

mysql 5.5 >select hex(25);
+---------+
| hex(25) |
+---------+
| 19      |
+---------+
1 row in set (0.00 sec)

mysql 5.5 >
[10 Sep 2012 18:05] Julien Duponchelle
I'm sorry if i am not clear. 

The problem in documentation you should invert DELETE_ROWS_EVENT and WRITE_ROWS_EVENT.

Thanks
[10 Sep 2012 20:53] MySQL Verification Team
Sorry and thank you for the feedback.
[2 Oct 2012 16:45] Paul DuBois
Correct URL is http://dev.mysql.com/doc/internals/en/replication-protocol.html#binlog-event-type
[5 Oct 2012 11:09] Jan Kneschke
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.