Give error 1478 ER_ILLEGAL_HA_CREATE_OPTION, but before gave syntax error. Parser.test appended with a test of various statements that should The ENGINE clause as optional for all statements listed above. The manual should therefore be updated marking Give error 1478, but before gave syntax error. It dumps one or more MySQL databases for backup or transfer to another SQL server. The mysqldump client utility performs logical backups, producing a set of SQL statements that can be executed to reproduce the original database object definitions and table data. Note that the ENGINE clause was optional before this fix even if thisĭoes not match the current version of the reference manual where it 4.5.4 mysqldump A Database Backup Program. Grammar to accept statements without extra clauses so that theĪbove statments give the proper error message used with engine=myisam:ĮRROR 1478 (HY000): Table storage engine 'MyISAM' does not support theĬreate option 'TABLESPACE or LOGFILE GROUP' Those clauses are all defined as optional. These statments used without any extra clauses gave syntax errors.Īdding one or more clauses would remove the syntax error, even if The problem was that syntaxĮrrors (1064) were mistakenly generated for the following statements: After review, it mayīe pushed to the relevant source trees for release in the nextīug #31293 create logfile group/tablespace returns OK with warningīug title slightly misleading. If ENGINE is added, we get the correct error.īugs System A patch for this bug has been committed. Jon Olav Hauglid Tried to replicate this bug using the mysql-6.0-runtime tree.ĮRROR 1478 (HY000): Table storage engine 'MyISAM' does not support the create option 'TABLESPACE or LOGFILE GROUP'ĮRROR 1064 (42000): You have an error in your SQL syntax check the manual thatĬorresponds to your MySQL server version for the right syntax to use near '' at line 1Īccording to the reference manual, this seems like the correct behaviour since the ENGINE parameter is not optional. Make "Error" level code appear as error instead of Warning. This should returns an error which is good but it should be error code 1475 Mysql> create tablespace ndb_ts1 add datafile 'ndb_ts1.dat' use logfile group ndb_lg1 ĮRROR 1064 (42000): You have an error in your SQL syntax check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 This should not return OK but should show the warning as error. | Error | 1475 | Table storage engine 'MyISAM' does not support the create option 'TABLESPACE or LOGFILE GROUP' | Query OK, 0 rows affected, 1 warning (0.00 sec) Mysql> create logfile group ndb_lg1 add undofile 'ndb_undo1' initial_size=32M To see what your default storage engine currently is do: mysql> SHOW engines MyISAM has long been the default, but someone might have changed it. Hence, if you are still affected, you may open a private report (GCP Private issues component) including your instance name and project for further investigation.Mysqld returns OK status with a warning from CREATE LOGFILE GROUP. That said, if you are using a second generation instance, it could be an intermittent issue at the time, or a missing flag (maybe at instance creation) that allowed using “myISAM”. However when trying the same on a First generation Cloud SQL instance it works fine, as per this document InnoDB is only recommended and not enforced. MySQL > create table test (a int) engine=myISAM ĮRROR 3161 (HY000): Storage engine MyISAM is disabled (Table creation is disallowed).Īnd that is consistent with this official troubleshooting guide where for second generation instances it throws this error. Trying to reproduce your results above, instead I got an error: As you mentioned, Innodb is only supported on a second generation Cloud SQL instance.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |