content_image/691976.jpg content_image/691984.jpg
<img src='content_image/691976.jpg'>

This system variable is deprecated (because DELAYED  inserts are not supported), and you should expect it to be removed in a future release. 

• disabled_storage_engines 

<img src='content_image/691984.jpg'>

This variable indicates which storage engines cannot be used to create tables or tablespaces. For example, to prevent new MyISAM  or FEDERATED  tables from being created, start the server with these lines in the server option file: 

[mysqld] disabled_storage_engines="MyISAM,FEDERATED" 

By default, disabled_storage_engines  is empty (no engines disabled), but it can be set to a comma-separated list of one or more engines (not case-sensitive). Any engine named in the value cannot be used to create tables or tablespaces with CREATE TABLE  or CREATE TABLESPACE , and cannot be used with ALTER TABLE ... ENGINE  or ALTER TABLESPACE ... ENGINE to change the storage engine of existing tables or tablespaces. Attempts to do so result in an ER_DISABLED_STORAGE_ENGINE  error. 

disabled_storage_engines  does not restrict other DDL statements for existing tables, such as CREATE INDEX , TRUNCATE TABLE , ANALYZE TABLE , DROP TABLE , or DROP TABLESPACE . This permits a smooth transition so that existing tables or tablespaces that use a disabled engine can be migrated to a permitted engine by means such as ALTER TABLE ... ENGINE permitted_engine . 

It is permitted to set the default_storage_engine  or default_tmp_storage_engine  system variable to a storage engine that is disabled. This could cause applications to behave erratically or fail, 

