I then tried to export the DB again, and finally it worked without any errors and without needing to pass additional parameters to the client:
I followed the dialogue’s guidance and configured MySQL Workbench’s settings to point to the version of mysqldump provided with the MariaDB version used by Local.Įdit > Preferences > Administration > Path to mysqldump Tool:Ĭ:\Program Files (x86)\Local\resources\extraResources\lightning-services\mariadb-10.4.10+4\bin\win32\bin\mysqldump.exe This allowed me to successfully create a an export of the DB, but the dialogue indicating a MySQL version mismatch was still displayed: "C:\Program Files\MySQL\MySQL Workbench 8.0 CE\mysqldump.exe" %* -column-statistics=0 Mac/Linux The solution is to create a script that runs mysqldump with the flag -column-statistics=0, then configure Workbench to point to the script: OFF
I did some Googling, and found this helpful post on ServerFault that explained a workaround for Windows/Mac/Linux. Mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"') FROM information_schema.COLUMN_STATISTICS WHERE SCHEMA_NAME = 'local' AND TABLE_NAME = 'wp_commentmeta' ': Unknown table 'column_statistics' in information_schema (1109)ġ1:52:38 Export of D:\dev\local-sites\mysqlexporttestmariadb\mysqlexporttestmariadb-.sql has finished with 1 errors Issue 1, Solution 1 Running: mysqldump.exe -defaults-file="c:\users\user1\appdata\local\temp\tmpnkltww.cnf" -user=root -host=127.0.0.1 -protocol=tcp -port=10142 -default-character-set=utf8 -skip-triggers "local" When attempting the export, a dialogue showing the following warning indicating a version mismatch was displayed: To export a DB using MySQL Workbench, connect to a DB server, then navigate to Server > Data Export. I didn’t have any problems running queries, so I didn’t think about it again. I made a mental note of the warning, but decided to proceed anyway.
When setting the site up in MySQL Workbench (my preferred MySQL client), I was presented with the following warning when testing the connection: My Local setup was configured to use MariaDB v10.4.10. (You know, like the warning message suggests when you try and do otherwise.) Use MySQL v5.7 or v8 when setting up a site in Local by Flywheel rather than using Maria DB. TL DR: Make sure that the version of mysqldump that your MySQL client (MySQL Workbench in my case) points to is the same as the DB version as what is used by the server. Unknown table 'column_statistics' in information_schema (1109) The first error I ran into when trying to export a DB was: Issue 1: MySQL database export error due to client/server version mismatch
#Export database mysql workbench download#
You can download this from GitHub and learn about Workbench Modeling on the MySQL site.I recently encountered a couple of frustrating MySQL database export errors and wanted to share the solutions I used with other folks, as well as document it for future me. Next, navigate to Tools -> Catalog -> Export Laravel 5 Migration, and a window will open with the migration ready for you to download: When you open it back up navigate to File -> New Model and add a basic structure for a table.
Next select the export-laravel-5-migrations.py file and restart the app.
#Export database mysql workbench install#
This works by downloading the plugin from GitHub, then open MySQL Workbench and go to the Scripting menu, Install Plugin/Module. When exported, each migration is generated and saved in its own, properly named, migration file. MySQL Workbench is a cross-platform GPL app that allows you to fully design and document your databases through the app.īrandon Eckenrode, created a plugin that allows you to export a MySQL Workbench model to Laravel 5 migrations that follow PSR-2 coding standards.
0 kommentar(er)
