MySQL Bugs: #13265: Adding --hex-blob to mysqlbinlog

Bug #13265	Adding --hex-blob to mysqlbinlog
Submitted:	16 Sep 2005 13:16	Modified:	9 Jun 2010 7:20
Reporter:	Mike Krejci	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Row Based Replication ( RBR )	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	bfsm_2006_11_02

Description:
I have had problems using mysqlbinlog where binary data (such as a jpg or such) is stored in VARBINARY or BLOB fields.  There is no --hex-blob feature in dumping the binary log file therefore creating bad insert or update statements that crash the restore.  Unless I'm missing something, this has caused alot of problems for me in restoring databases. 

How to repeat:
Create a table with a varbinary field - insert some binary data such as an image, or an AES_ENCRYPT function, use mysqlbinlog to dump the file to sql statements for restoring the data - the binary data will disrupt the text file creating invalid statements.

Suggested fix:
Add --hex-blob to mysqlbinlog

http://ingvar.blog.linpro.no/2008/10/27/point-in-time-recovery-of-mysql-with-binlog-and-bl...

Target Version is tagged as "6.x" in this bug. Is that a promise or a hint of something that maybe will be done if someone gets the time to do it?

Would it be possible to get this backported to earlier versions? We could really use this functionality for our 4.x and 5.x installations.

Duplicate of Bug#33048