VARBINARY type is recovered incorrectly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Data Recovery Tool for InnoDB |
Fix Committed
|
High
|
Aleksandr Kuzminsky |
Bug Description
CREATE TABLE `t1` (
`id` int NOT NULL auto_increment,
`f1` varchar(255) NOT NULL default '',
`f2` varbinary(255) NOT NULL,
`f3` BINARY(10) NOT NULL ,
`f4` CHAR(10) NOT NULL ,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=UTF8;
INSERT INTO t1 VALUES(NULL, 'aaa', 'bbb', 'ccc', 'dddd');
Recivered as:
$ ./constraints_
t2 1 "aaa" 626262626262 636363000000000
LOAD DATA INFILE '/home/
SET
f2 = UNHEX(@var_f2),
f3 = UNHEX(@var_f3);
Related branches
- Aleksandr Kuzminsky (community): Needs Fixing
-
Diff: 68 lines (+15/-3)4 files modifiedconstraints_parser.c (+2/-2)
create_defs.pl (+8/-0)
include/tables_dict.h (+2/-1)
print_data.c (+3/-0)
Changed in percona-data-recovery-tool-for-innodb: | |
milestone: | none → release-0.6 |
assignee: | nobody → Aleksandr Kuzminsky (akuzminsky) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in percona-data-recovery-tool-for-innodb: | |
status: | Confirmed → In Progress |
Changed in percona-data-recovery-tool-for-innodb: | |
status: | In Progress → Fix Committed |
Changed in percona-data-recovery-tool-for-innodb: | |
status: | In Progress → Fix Committed |
Hi Aleksandr,
I forgot a "break;" in print_data.c ...
--- print_data.c.orig 2011-09-28 22:38:51.039050435 +0000
+++ print_data.c 2011-09-28 22:39:05.359244526 +0000
@@ -214,6 +214,7 @@
+ break;
case FT_BLOB:
print_ hex((char* )value, len);