MySQL supports several storage engines that act as handlers for
different table types. MySQL storage engines include both those that
handle transaction-safe tables and those that handle
non-transaction-safe tables.
With MySQL 5.1, MySQL AB has introduced a new pluggable storage
engine architecture that allows storage engines to be loaded into
and unloaded from a running MySQL server.
I have tried setting the storage engine or table type in my.cnf as well as in the command line. These appear to be unknown variables in 4.1.7. This is on a Mac OS X 10.3.5 machine.
To set the default engine use this in the my.cnf file: default-table-type=NDBCLUSTER
From the command line use: --default-table-type=NDBCLUSTER
User Comments
I have tried setting the storage engine or table type in my.cnf as well as in the command line. These appear to be unknown variables in 4.1.7. This is on a Mac OS X 10.3.5 machine.
To set the default engine use this in the my.cnf file: default-table-type=NDBCLUSTER
From the command line use: --default-table-type=NDBCLUSTER
I've tried setting up the default storage engine in the configuration, and if I use:
table_type = innodb
or
storage_engine = innodb
mysqld would fail to restart. I've now used:
default-storage_engine = innodb
And it works. See also http://bugs.mysql.com/bug.php?id=19061
More information about how to pick the best MySQL Storage engine for your real life scenario:
http://www.softwareprojects.com/resources/programming/t-mysql-storage-engines-1470.html
Add your own comment.