-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Dump SQL Backup (MariaDB) Error #790
Comments
Try starting dbgate from the terminal to see if there's any useful output. This error doesn't stem from dbgate but instead underlying software. Giving the error a little look up I found a few things. This can be done with |
Hi @ProjectInfinity , Thanks for your instructions. In Terminal I got "ER_CANNOT_LOAD_FROM_TABLE_V2" My log in Terminal:
In Jet Brains DataGrip, I must add "--column-statistics=0" for dump sql backup |
I have found the reason. That's because MariaDB/MySQL Server had a previous upgrade/downgrade. This problem will occur.
In the remote database server we need to reconfigure. As you instructed with the command mariadb-upgrade or mysql_upgrade. But sometimes this command cannot be run with some Database Server Production. With other Database IDEs like Jet Brains Data Grip for example, they allow passing arguments to the sql dump command. Can I request a new feature, the ability to add arguments when using Backup Export/Import with SQL Dump like Data Grip does? For example, in my case, I can add the argument And we can add other parameters to make DbGate's SQL Dump more flexible. |
Thanks for the feedback. Perhaps being able to set dump arguments manually is a good workaround for those who have issues like yours. |
Hi,
I use DbGate 5.2.9 beta-2
When I backup my MariaDB Database by "Backup/export SQL dump" (The typo should be Backup/Export SQL Dump). I got the error.
Error running script: Cannot load from mysql.proc. The table is probably corrupted
The text was updated successfully, but these errors were encountered: