hi, Now I know it, sorry for the interruption :( The two mysql are compiled with different default character set parameters...
It's easy to get confused for having NULL in utf8 != NULL in gbk, though. Thank you 2009/3/24 Cui Shijun <rancp...@gmail.com>: > hi, > I tried this in mysql 5.1.22: > > mysql> create table t( value binary(16)) engine=innodb; > Query OK, 0 rows affected (0.00 sec) > > mysql> insert into t values( NULL ); > Query OK, 1 row affected (0.00 sec) > > mysql> checksum table t; > +-------+------------+ > | Table | Checksum | > +-------+------------+ > | IM.t | 2777151533 | > +-------+------------+ > 1 row in set (0.00 sec) > > In mysql 5.1.32, however: > > mysql> create table t( value binary(16)) engine=innodb; > Query OK, 0 rows affected (0.01 sec) > > mysql> insert into t values(NULL); > Query OK, 1 row affected (0.00 sec) > > mysql> checksum table t; > +-------+------------+ > | Table | Checksum | > +-------+------------+ > | IM.t | 3512059891 | > +-------+------------+ > 1 row in set (0.00 sec) > > > Any ideas? > Thank you > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
