Bug #107779 | MySQL Workbench has no way to export a database without PROCESS privilege | ||
---|---|---|---|
Submitted: | 6 Jul 2022 12:14 | Modified: | 11 Jun 2024 3:28 |
Reporter: | Nate Cartwright | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 8.0.29 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[6 Jul 2022 12:14]
Nate Cartwright
[6 Jul 2022 12:56]
MySQL Verification Team
Hello, Thank you for the bug report. Imho this is duplicate of Bug #100219, please see Bug #100219. Regards, Ashwini Patil
[18 Mar 2024 14:13]
Daniel Calliess
I'm experiencing the same problem in MySQL Workbench 8.0.32 and can't see how this is a duplicate of #100219. #100219 is about a problem with the "MySQL Server: mysqldump Command-line Client" and the current issue is affecting "MySQL Workbench".
[11 Jun 2024 3:28]
Nate Cartwright
This is not a duplicate, as that bug https://bugs.mysql.com/bug.php?id=100219 has to do with the update to mysqldump command. MySQL Workbench still needs to be updated to support the new --no-tablespaces flag available in mysqldump. There is no way to add that flag in MySQL Workbench. It should be added to the Advanced tab of MySQL Workbench, where the other flags for mysqldump live. This is basic functionality to be able to dump most modern databases on many web hosts.