MySQL Bugs: #18604: Illegal values permitted for ENGINE in CREATE LOGFILE GROUP

Bug #18604	Illegal values permitted for ENGINE in CREATE LOGFILE GROUP
Submitted:	29 Mar 2006 5:29	Modified:	26 Apr 2006 10:50
Reporter:	Mike Kruckenberg (Candidate Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.9-BK, 5.1.7	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
Playing with 5.1.7 disk-based storage I specified a non-NDB table for creating a logfile group. I don't believe this should be allowed.

mysql> create logfile group lg1 add undofile 'undofile.dat' initial_size = 20M undo_buffer_size = 1M engine=myisam;
Query OK, 0 rows affected (0.00 sec)

How to repeat:
running on 5.1.7 create a logfile group with engine=myisam.

Suggested fix:
raise error so users don't think something actually happened when issueing the statement.

Thank you for a bug report. Verified just as described with 5.1.9-BK (ChangeSet@1.2256, 2006-03-29 13:13:39+02:00) on SuSE Linux:

openxs@suse:~/dbs/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 to server version: 5.1.9-beta-debug

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

mysql> create logfile group lg1 add undofile 'undofile.dat' initial_size = 20M
    -> undo_buffer_size = 1M engine=myisam;
Query OK, 0 rows affected (0.00 sec)

It it a bug, according to the manual (http://dev.mysql.com/doc/refman/5.1/en/create-logfile-group.html):

"The ENGINE parameter determines the storage engine to be used by this logfile group, with engine being the name of the storage engine. In MySQL 5.1. engine must be one of the values NDB or NDBCLUSTER."

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

pushed to 5.1.10

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

Additional info:

Documented bugfix in 5.1.10 changelog. Closed.