Bug #23444 Binary Data is not escaped properly when written to binary log (mysqlbinlog?)

• Submitted: 18 Oct 2006 21:14
• Modified: 2 Nov 2006 15:01
• Reporter: Chris Calender
• Status: Not a Bug
• Category: MySQL Server: Command-line Clients
• Severity: S3 (Non-critical)
• Version: 5.0.24a, 5.0.26
• OS: Solaris (Solaris, Windows)
• Assigned to: Chris Calender
• CPU Architecture: Any
• Tags: bfsm_2006_11_02, binary data, escape, mysqlbinlog

[18 Oct 2006 21:14] Chris Calender

Description:
mysqlbinlog does not properly escape binary data from the binary log.

As you can see, binary data is written to the binary log.  However, when it is converted via mysqlbinlog (trying to perform point-in-time recovery), the resulting text file cannot be read.

C:\>mysql -u root -p < test.txt

ERROR 1064 (42000) at line 10: You have an error in your SQL syntax; check the m
anual that corresponds to your MySQL server version for the right syntax to use
near ''╨╧◄αí▒' at line 4

How to repeat:
See private comments.

[22 Oct 2006 17:50] Chris Calender

The fact is that binary log contains ESCAPED data, so this might not a bug in mysqlbinlog, but rather with the actual binary logging.  Thus I have changed the title appropriately.

[2 Nov 2006 15:01] Chris Calender

This is actually not a bug, at least not one that we cannot reproduce.

It appears to have been some sort of hiccup, as it has occurred only one time.