#Tableplus import sql how to
#Tableplus import sql install
#Tableplus import sql manual
#Tableplus import sql software

#Tableplus import sql software

I am admonished to check the MySQL documentation for the correct syntax to use, but I did not create that syntax, the same software complaining about the syntax actually created the syntax a few minutes before =)

#Tableplus import sql manual

This time it has nothing to do with reserved words, I export a pretty standard AspNet webapp db and already on the first table there is an error thrown concerning the syntax: 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 ''_EFMigrationsHistory' ( The same thing seems to happen with a completely different database. This is not the first issue I have with exporting and importing with TablePlus, I thought it was a pretty well renowned piece of software.

#Tableplus import sql how to

Perhaps it jumps on the reserved word timestamp but hey, if that same software created the export in the first place, shouldn't it know how to escape reserved words in the dump file that it just created? If I create a new database and try to import the file I just exported, I get the error: 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 ''transfers' ( You can also: Use ddev mysql or ddev psql or the mysql and psql commands inside the web and db. Here’s an example of a database import using DDEV: ddev import-db -file. You can read more about it here.Exporting a table with 22,245 rows using TablePlus, after which TablePlus tells me 'Export completed successfully'. Import a database with one command, from one of the following file formats.

#Tableplus import sql install

Install the client Configure access to your Cloud SQL instance.

After that, reconnect with TablePlus and you'll get the expected result. On this page Before you begin Use a MySQL client on a local machine or a Compute Engine VM. You can do this by going to the settings tab of your DO database, editing 'Global SQL modes' and then removing ANSI_QUOTES. As enabling this setting is considered to be bad practice, I decided to turn it off on the Digital Ocean side. It has the option ANSI_QUOTES enabled while the local MySQL (done via homebrew) doesn't have this option. The difference is caused by the default SQL mode set on Digital Ocean's databases. What I was expecting was this (note the difference between and'`): 1 CREATE TABLE `migrations ` ( 2 `id ` int unsigned NOT NULL AUTO_INCREMENT, 3 `migration ` varchar( 191) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL, 4 `batch ` int NOT NULL, 5 PRIMARY KEY ( `id `) 6 ) ENGINE =InnoDB AUTO_INCREMENT = 607 DEFAULT CHARSET =utf8mb4 COLLATE =utf8mb4_unicode_ci If you look at what is exported from the Digital Ocean database, you'll see that the export statements are liked this: 1 CREATE TABLE 'migrations' ( 2 'id' int unsigned NOT NULL AUTO_INCREMENT, 3 'migration' varchar( 191) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL, 4 'batch' int NOT NULL, 5 PRIMARY KEY ( 'id') 6 ) ENGINE =InnoDB AUTO_INCREMENT = 607 DEFAULT CHARSET =utf8mb4 COLLATE =utf8mb4_unicode_ci I finally (it took me quite a while) figured out what is causing this: MySQL settings. However, when importing this on my local machine, it failed with: 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 ''migrations' (… To export, I select one or more table in TablePlus, right-click on them and then choose export to an SQL file. The setup was that I'm exporting data from a Digital Ocean managed MySQL server and then import this into a local install of MySQL on my mac. I recently spend a lot of time figuring out why exporting a table from TablePlus was giving me the incorrect output.