Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL)
Description
The mysqldump tool included with MariaDB client generates SQL for creating a temporary table with the MyISAM engine.
|
client/mysqldump.c#L3283-L3292 |
/* |
Stand-in tables are always MyISAM tables as the default
|
engine might have a column-limit that's lower than the
|
number of columns in the view, and MyISAM support is
|
guaranteed to be in the server anyway.
|
*/
|
fprintf(sql_file, |
"\n) ENGINE=MyISAM */;\n" |
"SET character_set_client = @saved_cs_client;\n"); |
This is problematic when trying to import this into Azure MariaDB service, since that doesn't support MyISAM.
I have seen that MySQL's mysqldump produces temporary VIEWs with SELECT 1 AS fieldname, that might be a better option to consider as well..
Attachments
Activity
Aria was the logical change from MyISAM.
Right, Aria isn't sufficient a substitution if its not there on Azure. I haven't found column limits for InnoDB or Memory engine which the comment describes.
SQL_MODE disabling NO_ENGINE_SUBSTITUTION is probably a good change to include too as Aria isn't necessary there.
I took the VIEW based approach as suggested.
Thanks for the bug report.
Can I please get a review of PR 2214.