Bug #19061 storage_engine can't be set in my.cnf - documentation issue?
Submitted: 12 Apr 2006 19:47 Modified: 13 Apr 2006 13:17
Reporter: Christian Becker Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0.19-max OS:Linux (SuSE Linux 9)
Assigned to: MC Brown CPU Architecture:Any
Triage: D4 (Minor)

[12 Apr 2006 19:47] Christian Becker
Description:
See http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html :

"If you omit the ENGINE or TYPE option, the default storage engine is used. Normally, this is MyISAM, but you can change it by using the --default-storage-engine or --default-table-type server startup option, or by setting the storage_engine or table_type system variable. "

I experience the same problem as the commenter on that page - in fact, specifying "storage_engine=NDBCLUSTER" in my.cnf (mysqld section) causes mysqld to fail at startup.

How to repeat:
5.0.19-max

my.cnf:

# Options for mysqld process:
[MYSQLD]
ndbcluster                      # run NDB engine
ndb-connectstring="nodeid=12,xx.xx.xx.xx,xx.xx.xx.xx"
storage_engine=NDBCLUSTER

# Options for ndbd process:
[NDBD]
ndb-connectstring="nodeid=22,xx.xx.xx.xx,xx.xx.xx.xx"

Suggested fix:
Using "default-storage_engine" instead works as expected.
[12 Apr 2006 19:48] Christian Becker
added version/os
[12 Apr 2006 23:17] Hartmut Holzgraefe
Verified, in my.cnf it is default_table_type, table_type is the name of the runtime variable reported by SHOW VARIABLES and changeable using SET later
[13 Apr 2006 13:17] MC Brown
I have checked this and updated the documentation for 4.1, 5.0 and 5.1 accordingly. I've also added examples for setting the variable for the current session to control the default engine used.