Bug #8830 mysqldump --skip-extended-insert causes --hex-blob to dump wrong values

• Submitted: 27 Feb 2005 12:26
• Modified: 7 Mar 2005 16:17
• Reporter: Alexander Keremidarski
• Status: Closed
• Category: Client
• Severity: S2 (Serious)
• Version: 4.1
• Assigned to: Sinisa Milivojevic

[27 Feb 2005 12: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 20: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 15:59] Sinisa Milivojevic

Pushed in a changeset 1.2092