Bug #8830 mysqldump --skip-extended-insert causes --hex-blob to dump wrong values
Submitted: 27 Feb 2005 11:26 Modified: 7 Mar 2005 15:17
Reporter: Alexander Keremidarski Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S2 (Serious)
Version:4.1 OS:Any
Assigned to: CPU Architecture:Any

[27 Feb 2005 11:26] Alexander Keremidarski 
Description:
See synopsis

How to repeat:
CREATE TABLE t (b BLOB);
INSERT INTO t VALUES(0x602010000280100005E71A);
SELECT HEX(b) FROM t;

+------------------------+
| HEX(b)                 |
+------------------------+
| 602010000280100005E71A |
+------------------------+

mysqldump bugs t --skip-extended-insert --hex-blob -t | grep INSERT 
INSERT INTO `t` VALUES (0x6020100002FFFFFF80100005FFFFFFE71A);

mysqldump bugs t --hex-blob -t | grep INSERT
INSERT INTO `t` VALUES (0x602010000280100005E71A);
[5 Mar 2005 19:54] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/22697
[7 Mar 2005 14:59] MySQL Verification Team 
Pushed in a changeset 1.2092