From 982bd00d481333c44e6aee59fc667f8de155a612 Mon Sep 17 00:00:00 2001 From: unknown Date: Sat, 21 May 2005 18:44:51 +0300 Subject: [PATCH] ha_innodb.cc: The natural InnoDB type for NEWDECIMAL is FIXBINARY, not BINARY, since there probably is no benefit from stripping trailing bytes 0x20; note that tables created with 5.0.6 and containing DECIMAL do not need to be rebuilt, as BINARY works as well; note that because of Jani's fix to bug 10465, tables created with 5.0.? - 5.0.5 DO NEED TO BE REBUILT if they contain DECIMAL sql/ha_innodb.cc: The natural InnoDB type for NEWDECIMAL is FIXBINARY, not BINARY, since there probably is no benefit from stripping trailing bytes 0x20; note that tables created with 5.0.6 and containing DECIMAL do not need to be rebuilt, as BINARY works as well; note that because of Jani's fix to bug 10465, tables created with 5.0.? - 5.0.5 DO NEED TO BE REBUILT if they contain DECIMAL --- sql/ha_innodb.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql/ha_innodb.cc b/sql/ha_innodb.cc index 0004503e1e5..381c9c28a79 100644 --- a/sql/ha_innodb.cc +++ b/sql/ha_innodb.cc @@ -2606,7 +2606,7 @@ get_innobase_type_from_mysql_type( return(DATA_MYSQL); } case FIELD_TYPE_NEWDECIMAL: - return(DATA_BINARY); + return(DATA_FIXBINARY); case FIELD_TYPE_LONG: case FIELD_TYPE_LONGLONG: case FIELD_TYPE_TINY: