Bug #7310 "multi_update" fails when InnoDB is missing

• Submitted: 15 Dec 2004 9:17
• Modified: 4 Feb 2005 17:36
• Reporter: Lenz Grimmer
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 4.1.8
• OS: Any (All)
• Assigned to: Antony Curtis
• CPU Architecture: Any

[15 Dec 2004 9:17] Lenz Grimmer

Description:
When running the test suite of a 4.1.8-classic binary (which does not include InnoDB), the "multi_update" test fails with the following diff:

multi_update                   [ fail ]

Errors are (from /build/mysqldev/build/test/mysql-classic-4.1.8-pc-linux-i686/mysql-test/var/log/mys
qltest-time) :
/build/mysqldev/build/test/mysql-classic-4.1.8-pc-linux-i686/bin/mysqltest: At line 449: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/multi_update.result       Tue Dec 14 18:05:02 2004
--- r/multi_update.reject       Wed Dec 15 10:36:41 2004
***************
*** 468,477 ****
--- 468,481 ----
  aclid bigint not null primary key,
  status tinyint(1) not null
  ) engine = innodb;
+ Warnings:
+ Warning       1266    Using storage engine MyISAM for table 't1'
  create table t2 (
  refid bigint not null primary key,
  aclid bigint, index idx_acl(aclid)
  ) engine = innodb;
+ Warnings:
+ Warning       1266    Using storage engine MyISAM for table 't2'
  insert into t2 values(1,null);
  delete t2, t1 from t2 left join t1 on (t2.aclid=t1.aclid) where t2.refid='1';
  drop table t1, t2;
-------------------------------------------------------

How to repeat:
Configure a binary using "--without-innodb" and run the test suite. Observe the diff mentioned above.

Suggested fix:
The test needs to make sure that InnoDB is really included

[4 Feb 2005 17:36] Antony Curtis

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html