Platform : Windows NT 4.0 MySQL server version: 3.23.36

Description: mysqlbinlog has a bug translating an insert/update statement with a BLOB that contains the value 0x0A. This value is translated to 0x0D 0x0A (probably because win32 end of line is CRLF instead of LF in unix).

Test-To-Repeat: I have used a Java program that inserts a byte array into a BLOB column. The byte array was 256 bytes long and contained the values 0-255 (I've read the byte array from the table and it was identical). I've used mysqlbinlog to convert the binary log created as a result of my previous insert and replayed it into the database using the command 'mysql -e "source logfile" '. Then when I read the byte array it's length was 257 and in the 10th place that value was 0x0D instead of 0x0A, and indeed while looking at the text log using a hex editor I saw ...08 09 0D 0A 0B ... I've also examined the binary log itself and the sequence looks fine.