Bug #1464 SET table_type = badtype doesn't produce warning
Submitted: 2 Oct 2003 10:17 Modified: 9 Dec 2003 17:21
Reporter: Paul Dubois Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1 OS:
Assigned to: Antony Curtis CPU Architecture:Any

[2 Oct 2003 10:17] Paul Dubois
As of MySQL 4.1, attempting to create a table with a
type that the server doesn't support results in a warning.
For example, if have_isam is NO, this happens:

mysql> create table t (i int) type = isam;
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> show warnings;
| Level   | Code | Message                                   |
| Warning | 1265 | Using storage engine MYISAM for table 't' |
1 row in set (0.00 sec)

That's as it should be. However, this behavior does not
appear to extend to setting the default table type, even
though it's a similar issue:

mysql> set table_type = isam;
Query OK, 0 rows affected (0.00 sec)

mysql> select @@table_type;
| @@table_type |
| ISAM         |
1 row in set (0.01 sec)

This shouldn't work, or at least should produce a
warning, shouldn't it?

How to repeat:
See above.
[12 Nov 2003 0:52] Sergei Golubchik
it's a minor issue, so we'll fix it in 5.0, where the code for managing handlers will be (is) reworked
[9 Dec 2003 17:21] 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

Additional info:

Fixed as part of WorkLog#1280