Bug #7661 'classic' shows different test effects which must be cared for
Submitted: 4 Jan 2005 13:54 Modified: 22 Feb 2005 20:55
Reporter: Joerg Bruehe Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.3-pre OS:Any (Any)
Assigned to: Ramil Kalimullin CPU Architecture:Any

[4 Jan 2005 13:54] Joerg Bruehe
Description:
InnoDB has some properties which differ from other handlers. When the test suite is run using a 'classic' build (= without InnoDB), some tests show different results from all other runs, so they fail.

Examples:

'multi_update.result' contains these lines:
---
drop table t1,t2;
create table t1 (
aclid bigint not null primary key,
status tinyint(1) not null
) engine = innodb;
create table t2 (
refid bigint not null primary key,
aclid bigint, index idx_acl(aclid)
) engine = innodb;
---
Of course, both get warning 1266 in a 'classic' test.

'type_bit.result' contains these lines:
---
create table t1 (a bit, key(a)) engine=innodb;
ERROR 42000: The storage engine for the table doesn't support BIT FIELD
---
In 'classic', the 'engine=' option is ignored, the table gets created, ...

How to repeat:
Run the test suite for 'classic'.
[21 Feb 2005 11:44] Joerg Bruehe
Symptom in today's build, all 'classic' runs:

.../mysqltest: At line 30: query 'create table t1 (a bit, key(a)) engine=innodb' succeeded - should have failed with errno 1178...
.../mysqltest: At line 32: query 'create table t1 (a bit(64))' failed: 1050: Table 't1' already exists
[21 Feb 2005 14:08] Ramil Kalimullin
fixed in 5.0.3-alpha
[22 Feb 2005 20:55] Paul DuBois
No doc change needed.