Mamp pro windows mysql 5.66/16/2023 You might like to consider differences in character-set and as mentioned in this question.Īs you suggested that the error is not because of the reserve words, I'd ask you to check if that's the encoding issues as mentioned here. To allow them you need to use option -allow-keywords in your mysqldump command. ![]() I've seen things like those happening due to reserve words (keywords). cnf file 0 5242880 bytes!ġ60802 9:38:04 Plugin 'InnoDB' init function returned error.ġ60802 9:38:04 Plugin 'InnoDB' registration as a STORAGE ENGINE failed.ġ60802 9:38:04 Unknown/unsupported storage engine: InnoDBġ60802 9:38:04 /Applications/MAMP/Library/bin/mysqld: Shutdown completeġ60802 09:38:04 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended ![]() ib_logfile0 is of different size 0 50331648 bytes 160802 09:38:03 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysqlġ60802 9:38:04 Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql/ is case insensitiveġ60802 9:38:04 Plugin 'FEDERATED' is disabled.ġ60802 9:38:04 InnoDB: The InnoDB memory heap is disabledġ60802 9:38:04 InnoDB: Mutexes and rw_locks use GCC atomic builtinsġ60802 9:38:04 InnoDB: Compressed tables use zlib 1.2.3ġ60802 9:38:04 InnoDB: Initializing buffer pool, size = 128.0Mġ60802 9:38:04 InnoDB: Completed initialization of buffer pool I've tried other reccomendations on other threads with same issue, but no luck.
0 Comments
Leave a Reply. |