MySQL Bugs: #22708: Error message doesn't refer to storage engine unsupported

Bug #22708	Error message doesn't refer to storage engine unsupported
Submitted:	26 Sep 2006 18:59	Modified:	27 Mar 2008 19:03
Reporter:	Peter Gulutzan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.1.12-beta-debug	OS:	Linux (SUSE 10.0 / 64-bit)
Assigned to:	Sergey Vojtovich	CPU Architecture:	Any

Description:
I create a table with engine=innodb,
Later I try to access it, with a server
that doesn't support innodb.
The error message is 1017 "Can't find file".

I create a table with engine=archive.
Later I try to access it, with a server
that doesn't support archive.
The error message is 1017 "Can't find file".

I create a table with partitioning.
Later I try to access it, with a server
that doesn't spport partitioning.
The error message is

I create a table with engine=solid.
Later I try to access it, with a server
that doesn't support solid.
The error message is: 1037 Out of Memory, or 2013 crash.

In such cases, the error message should say:
the engine needed for this table is not supported

A similar message should appear in
information_schema.tables.table_comment.

How to repeat:
With a server that supports InnoDB,
CREATE TABLE t1 (s1 INT) engine=innodb;
With a server that doesn't support InnoDB,
(e.g. started with --skip-innodb),
SELECT * FROM t1;

With a server that supports archive,
CREATE TABLE t2 (s1 INT) engine=archive;
With a server that doesn't support archive,
(for example an earlier MySQL version),
SELECT * FROM t2;

With a server that supports partitioning,
CREATE TABLE t3 (s1 INT) PARTITION BY HASH(s1);
With a server that doesn't support partitioning,
(for example an earlier MySQL version),
SELECT * FROM t3;

With a server that supports solid,
(I used "beta 3" downloadable from solidtech.com),
CREATE TABLE t4 (s1 INT) engine=solid;
With a server that doesn't support solid,
(for example the regular MySQL distribution),
SELECT * FROM t4;
DROP TABLE t4;

Thank you for a bug report. Verified just as described.

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/39212

ChangeSet@1.2618, 2007-12-04 18:40:12+04:00, svoj@mysql.com +1 -0
  BUG#22708 - Error message doesn't refer to storage engine unsupported
  
  When openning a table with unsupported (disabled or not compiled)
  storage engine, confusing error message is returned.
  
  Return better error message when we're attempting to open a table
  that uses unsupported engine.

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/39988

ChangeSet@1.2618, 2007-12-14 17:05:27+04:00, svoj@mysql.com +1 -0
  BUG#22708 - Error message doesn't refer to storage engine unsupported
  
  When openning a table with unsupported (disabled or not compiled)
  storage engine, confusing error message is returned.
  
  Return better error message when we're attempting to open a table
  that uses unsupported engine.

Pushed into 5.1.24-rc

Pushed into 6.0.5-alpha

Noted in 5.1.24, 6.0.5 changelogs.

The server produced a confusing error message when attempting to open 
a table that required a storage engine that was not loaded.

Also documented in 5.1.23-ndb-6.3.11 changelog.