MySQL Bugs: #31425: CREATE TABLE ... TYPE=<engine> doesn't give warning anymore

Bug #31425	CREATE TABLE ... TYPE=<engine> doesn't give warning anymore
Submitted:	5 Oct 2007 19:22	Modified:	5 Nov 2007 21:54
Reporter:	Tobias Asplund	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.1.22	OS:	MacOS
Assigned to:		CPU Architecture:	Any

Description:
TYPE gives an empty warning when used in a create table statement.

How to repeat:
mysql> create table t5 ( a int) type=innodb;
Query OK, 0 rows affected, 1 warning (0.37 sec)

mysql> show warnings;
1 row in set (0.00 sec)

Suggested fix:
fix for http://bugs.mysql.com/bug.php?id=17501 seems to have removed the warning, but it still gives one. Restore the old warning :)

Thank you for the bug report. I can't repeat on Linux with source server.
Are you tested today source server?

[miguel@skybr 5.1]$ bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.1.23-beta-debug Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create table t5 ( a int) type=innodb;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> show warnings;
+---------+------+-----------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                     |
+---------+------+-----------------------------------------------------------------------------------------------------------------------------+
| Warning | 1287 | The syntax 'TYPE=storage_engine' is deprecated and will be removed in MySQL 5.2. Please use 'ENGINE=storage_engine' instead | 
+---------+------+-----------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql>

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".