8 messages in com.mysql.lists.bugsBug in mysqlbinlog (win32)
FromSent OnAttachments
Ze'ev Bubis18 Apr 2001 07:02 
Michael Widenius18 Apr 2001 09:42 
Michael Widenius19 Apr 2001 13:07 
Ze'ev Bubis20 Apr 2001 07:41 
Michael Widenius20 Apr 2001 12:47 
Timothy Smith20 Apr 2001 13:03 
Michael Widenius21 Apr 2001 23:54 
Ze'ev Bubis22 Apr 2001 00:54 
Subject:Bug in mysqlbinlog (win32)
From:Michael Widenius (mon@mysql.com)
Date:04/18/2001 09:42:59 AM
List:com.mysql.lists.bugs

Hi!

"Ze'ev" == Ze'ev Bubis <zee@myrealbox.com> writes:

Ze'ev> Platform : Windows NT 4.0 Ze'ev> MySQL server version: 3.23.36

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

Ze'ev> Test-To-Repeat: Ze'ev> I have used a Java program that inserts a byte array into a BLOB column. Ze'ev> The byte array was 256 bytes long and contained the values 0-255 (I've Ze'ev> read the byte array from the table and it was identical). Ze'ev> I've used mysqlbinlog to convert the binary log created as a result of Ze'ev> my previous insert and replayed it into the database using the command Ze'ev> 'mysql -e "source logfile" '.

Ze'ev> Then when I read the byte array it's length was 257 and in the 10th Ze'ev> place that value was 0x0D instead of 0x0A, and indeed while looking at Ze'ev> the text log using a hex editor I saw ...08 09 0D 0A 0B ...

Hod did you create the text log? Can you send me a copy of the binary log file ?

Ze'ev> I've also examined the binary log itself and the sequence looks fine.

Could you check the version of your 'mysql' client with:

mysql -V (It should be 11.14 or newer)

Some old 'mysql' clients had a long time ago the problem that the 'source' command didn't open the file in binary mode.

Regards, Monty