Bug #11895 ctype_utf8 fails when InnoDB not available
Submitted: 13 Jul 2005 1:59 Modified: 15 Jul 2005 12:49
Reporter: Jim Winstead Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.13bk OS:
Assigned to: Lenz Grimmer CPU Architecture:Any

[13 Jul 2005 1:59] Jim Winstead
Description:
ctype_utf8 fails when InnoDB is not included (like a 'Classic' build) because a warning is issued when it attempts to create an innodb table.

How to repeat:
ctype_utf8                     [ fail ]

Errors are (from /Users/mysqldev/jimw/mysql-4.1.13/mysql-test/var/log/mysqltest-time) :
/Users/mysqldev/jimw/mysql-4.1.13/client/mysqltest: At line 813: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/ctype_utf8.result Wed Jul 13 04:32:45 2005
--- r/ctype_utf8.reject Wed Jul 13 04:58:51 2005
***************
*** 933,938 ****
--- 933,940 ----
  `created` datetime NOT NULL default '0000-00-00 00:00:00',
  UNIQUE KEY `PK_user` (`msisdn`)
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+ Warnings:
+ Warning       1266    Using storage engine MyISAM for table 't2'
  INSERT INTO t2 VALUES ('1234567890',2,'2005-05-24 13:53:25');
  SELECT content, t2.msisdn FROM t1, t2 WHERE t1.msisdn = '1234567890';
  content       msisdn
-------------------------------------------------------
Please follow the instructions outlined at
http://www.mysql.com/doc/en/Reporting_mysqltest_bugs.html
to find the reason to this problem and how to report this.
[15 Jul 2005 12:49] Lenz Grimmer
Fix was pushed into 4.1 and 5.0

http://lists.mysql.com/internals/27085