Bug #99417 | MySQL Workbench: Unresponsive several minutes after each "use DB" statement | ||
---|---|---|---|
Submitted: | 2 May 2020 11:13 | Modified: | 4 May 2020 7:47 |
Reporter: | Danny Sevcik | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
Version: | 8.0.19-1ubuntu18.04, 8.0.20 | OS: | Debian (10 Buster) |
Assigned to: | CPU Architecture: | x86 (64bit) |
[2 May 2020 11:13]
Danny Sevcik
[4 May 2020 7:47]
MySQL Verification Team
Hello Danny Sevcik, Thank you for the report and feedback. regards, Umesh
[18 Nov 2020 19:03]
Vince Vaughn
I'm having the same problem on 8.0.21. I would post the build but your [redacted] 'About' interface closes everytime you click or press a key. This is an unacceptable behavior that was not present in older versions. I am on a very fast connection that may as well be local, however the Server has over 100 databases and each database has hundreds of tables. Waiting several minutes to run a simple query is unacceptable, and this may be the final nail in the coffin for us continuing to use MySQL. I'm well aware you guys don't care if I use the software or not, but this #wontfix attitude is very frustrating. Having to wait several minutes to run even a basic query can cost thousands of dollars when time is critical. Sorry for the stern post, but seriously you guys, this can't be hard to fix or add an option to work around.
[19 Nov 2020 18:07]
Dave Li
Experiencing the very same issue. We had to abandon this tool in our teams until this issue is resolved. When it is we might reconsider getting back to but I am not quite sure, we have conservaive policy and we don't like jumping tools without serious reasons. Looks like it was meant for small size projects, probably people running their WordPress sites. The tool is completely unusable with serious large scale projects. Sad. It had a potential and I can see that lot of work went into it already.