Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.11, 11.1(EOL), 11.2(EOL), 11.4, 11.5(EOL), 11.6(EOL)
Description
MariaDB [test]> select @@enforce_storage_engine;
|
+--------------------------+
|
| @@enforce_storage_engine |
|
+--------------------------+
|
| InnoDB |
|
+--------------------------+
|
1 row in set (0.00 sec)
|
|
|
MariaDB [test]> set sql_mode=NO_ENGINE_SUBSTITUTION;
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
MariaDB [test]> create table t (i int) engine=MyISAM;
|
ERROR 1286 (42000): Unknown storage engine 'MyISAM'
|
It is of course expected that CREATE would produce an error, just not the error. If there is no suitable one, maybe it should be created.
Attachments
Issue Links
- relates to
-
MDEV-6858 enforce_storage_engine option
-
- Closed
-
Activity
The massage is wrong, there should name of the option passed not name of the engine
rucha174 Hi! It looks like the patch only needs a small change (i.e. ERROR HY000: The MariaDB server is running with the enforce_storage_engine option so it cannot execute this statement) to finish? Thanks!
let's use ER_OPTION_PREVENTS_STATEMENT