Bug #77204 Two data types are not decoded correctly through MySQL Binlog Events
Submitted: 1 Jun 2015 9:10 Modified: 12 Nov 2015 13:56
Reporter: Neha Kumari Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities: Binlog Events Severity:S3 (Non-critical)
Version:1.0.0 OS:Any
Assigned to: CPU Architecture:Any

[1 Jun 2015 9:10] Neha Kumari
Description:
These two data types are not decoded correctly through MySQL Binlog Events:

-MYSQL_TYPE_STRING
-MYSQL_TYPE_VARCHAR(for metadata length greater than 255)

When we try to extract the information about the data inserted and print them in human readable format the above two data types contain some garbage data along with the required data.

How to repeat:
Following are the steps to create an example program to repeat this:
- Save the Table_map_event in a map using table_id as the key.
- Create a row_event_set using the above saved Table_map_event and
  the write/delete/update rows_event which will hold all the rows which were   
  affected.
- Now iterate over this row_event_set, each element in this set will represent  
  a row.
- Extract the data and print them in human readable format along with the 
  required metadata.

Compare this result with the outcome of mysqlbinlog utility of
MySQL Server to check for the corrupted data in case of Binlog Events.
[2 Jun 2015 7:19] Mats Kindahl
Thank you for the bug report, verified as described.
[12 Nov 2015 13:56] David Moss
This seems to be related to internal only stuff. Therefore closing without change to the docs.