Bug #22436 Four tests require "innodb" to be configured, fail in "classic" build
Submitted: 18 Sep 2006 9:55 Modified: 6 Nov 2006 14:46
Reporter: Joerg Bruehe Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:5.0.25 OS:Any (All)
Assigned to: Magnus Blåudd CPU Architecture:Any

[18 Sep 2006 9:55] Joerg Bruehe
Description:
Now that we again build a "classic" configuration in 5.0, 
we get failing tests because they assume InnoDB to be configured:

-------------------------------------------------------
*** r/create.result
--- r/create.reject
***************
*** 770,775
  create table t1(f1 varchar(800) binary not null, key(f1)) engine = innodb
  character set utf8 collate utf8_general_ci;
  Warnings:
! Warning       1071    Specified key was too long; max key length is 765 bytes
  insert into t1 values('aaa');
  drop table t1;
--- 770,776
  create table t1(f1 varchar(800) binary not null, key(f1)) engine = innodb
  character set utf8 collate utf8_general_ci;
  Warnings:
! Warning       1266    Using storage engine MyISAM for table 't1'
! Warning       1071    Specified key was too long; max key length is 999 bytes
  insert into t1 values('aaa');
  drop table t1;
-------------------------------------------------------

-------------------------------------------------------
*** r/lock_multi.result
--- r/lock_multi.reject
***************
*** 83,88
--- 83,90
  UNLOCK TABLES;
  DROP TABLE t1;
  create table t1 (f1 int(12) unsigned not null auto_increment, primary key(f1)) engine=innodb;
+ Warnings:
+ Warning       1266    Using storage engine MyISAM for table 't1'
  lock tables t1 write;
   alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_i
ncrement=0; alter table t1 auto_increment=0; //
   alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_i
ncrement=0; alter table t1 auto_increment=0; //
-------------------------------------------------------

-------------------------------------------------------
*** r/sp.result
--- r/sp.reject
***************
*** 4787,4792
--- 4787,4794
  drop table t3|
  drop procedure bug16887|
  create table t3 (f1 int, f2 varchar(3), primary key(f1)) engine=innodb|
+ Warnings:
+ Warning       1266    Using storage engine MyISAM for table 't3'
  insert into t3 values (1,'aaa'),(2,'bbb'),(3,'ccc')|
  CREATE FUNCTION bug13575 ( p1 integer )
  returns varchar(3)
-------------------------------------------------------

-------------------------------------------------------
*** r/view.result
--- r/view.reject
***************
*** 1981,1986
--- 1981,1988
  drop table t1;
  set sql_mode='strict_all_tables';
  CREATE TABLE t1 (col1 INT NOT NULL, col2 INT NOT NULL) ENGINE = INNODB;
+ Warnings:
+ Warning       1266    Using storage engine MyISAM for table 't1'
  CREATE VIEW v1 (vcol1) AS SELECT col1 FROM t1;
  CREATE VIEW v2 (vcol1) AS SELECT col1 FROM t1 WHERE col2 > 2;
  INSERT INTO t1 (col1) VALUES(12);
***************
*** 2033,2038
--- 2035,2042
  drop view v1;
  drop table t1;
  CREATE TABLE t1 (f1 char) ENGINE = innodb;
+ Warnings:
+ Warning       1266    Using storage engine MyISAM for table 't1'
  INSERT INTO t1 VALUES ('A');
  CREATE VIEW  v1 AS SELECT * FROM t1;
  INSERT INTO t1 VALUES('B');
-------------------------------------------------------

How to repeat:
Build "classic" and test it.

Suggested fix:
Split these tests into a general part and one requiring InnoDB,
or make them completely requiring InnoDB.
[28 Sep 2006 13:13] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/12717

ChangeSet@1.2273, 2006-09-28 15:13:40+02:00, msvensson@neptunus.(none) +7 -0
  Bug#22436 Four tests require "innodb" to be configured, fail in "classic" build
   - Disable warnings when creating the "innodb" tables if it works anyway.
   - Move test that are really innodb dependent to innodb_mysql
[26 Oct 2006 18:20] Magnus Blåudd
Pushed to 5.0-maint and 5.1-maint
[6 Nov 2006 14:46] Paul DuBois
Test suite change. No changelog entry needed.