Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#59656 - [mysql-workbench] Workbench unable to get mysqldump version
Attached to Project:
Community Packages
Opened by Laurent HOAREAU (laurent_waro) - Tuesday, 14 August 2018, 09:20 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 17 May 2023, 21:27 GMT
Opened by Laurent HOAREAU (laurent_waro) - Tuesday, 14 August 2018, 09:20 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 17 May 2023, 21:27 GMT
|
DetailsDescription: When you try to make a dump of a database, mysql-workbench say "Workbench unable to get mysqldump version. Please verify the log file for more information"
Additional info: * package version(s) : 8.0.12-3 Steps to reproduce: On an opend connection, go to "Administration", next Data/Export |
This task depends upon
This function was introduced to Mariadb in version 10.2.3.
ArchLinux uses Mariadb version 10.1.35 (packet "mariadb-clients" in "extra" repository).
Workaround:
Chance "Preferences" -> "Administration" -> "Path to mysqldump tool" to "/usr/bin/mysqldump".
Now I change in "Preferences" -> "Administration" -> "Path to mysqldump tool" to "/usr/bin/mysqldump". But mysql-workbench still report to me the same error.
and updating the Workbench which is not able to work with the existing Packages in the STABLE repo.
QC wouldn't have any nice words for you.
In my eyes, WB 8+ is not usable due to to many bugs for any serious user.
In the testing repo I would tolerate this issues but not on a stable/productive system.