VARBINARY type is recovered incorrectly

[Aleksandr Kuzminsky]

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_parser -5Uf ./pages-1314783910/FIL_PAGE_INDEX/0-68/0-00000003.page
t2 1 "aaa" 626262626262 6363630000000000000063636300000000000000 "dddd "

LOAD DATA INFILE '/home/akuzminsky/src/percona-innodb-recovery-tool/With_binary_support/dumps/default/t2' REPLACE INTO TABLE `t2` FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 't2\t' (id, f1, @var_f2, @var_f3, f4)
SET
    f2 = UNHEX(@var_f2),
    f3 = UNHEX(@var_f3);

[Yves Trudeau (y-trudeau)]

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 @@

                 case FT_BIN:
                         print_hex((char*)value, len);
+ break;

   case FT_BLOB:
               print_hex((char*)value, len);

[Aleksandr Kuzminsky (akuzminsky)]

No fixed. "break;" was lost after FT_BIN:

230
                case FT_BIN:

231
                        print_hex((char*)value, len);

232

230
233
                case FT_BLOB: