![]() In this case both source databases are hosted with DigitalOceans service "database cluster", if it makes a difference =). ![]() 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 =) Then hit commit (Cmd + S) to save the change to the server. 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" ( Click on the database icon (or use shortcut key cmd + K), right click on the database name and choose Rename. 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. 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" ( Exporting a table with 22,245 rows using TablePlus, after which TablePlus tells me "Export completed successfully".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |