Bug #77479 Printing row data in human readable format
Submitted: 25 Jun 2015 8:55 Modified: 12 Nov 2015 13:58
Reporter: NEHA KUMARI Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities: Binlog Events Severity:S4 (Feature request)
Version:1.0.0 OS:Any
Assigned to: CPU Architecture:Any

[25 Jun 2015 8:55] NEHA KUMARI 
Description:
The row data should be emitted as a string in the form of sequence of ASCII characters 65, 66, 1
  
- This is suitable for putting the string into files for later
  processing
- It is also suitable for log files that are intended for humans but
  where the character set is not ASCII so the string can contain
  non-ASCII character that should be printed to the log file, e.g.,
  "Flórez".

How to repeat:
N/A

Suggested fix:
Write a program which takes the Row_event data and serialize it in a string.
[7 Aug 2015 10:43] NEHA KUMARI 
Each data type should be able to decoded and be convertible to strings, in case of string data type we might have some non-printable character so that should be handled as well.
[12 Aug 2015 19:09] NEHA KUMARI 
Added printable support for following data types:

MYSQL_TYPE_INT24,MYSQL_TYPE_NULL 
MYSQL_TYPE_DATE, MYSQL_TYPE_TIME, 
MYSQL_TYPE_YEAR, MYSQL_TYPE_BIT,
MYSQL_TYPE_SET, MYSQL_TYPE_ENUM.
[12 Nov 2015 13:58] David Moss 
This seems to be related to internal only stuff. Therefore closing without change to the docs.