Bug #96357 WB reports objects "could not be fetched"

• Submitted: 28 Jul 2019 8:09
• Modified: 31 Jul 2019 14:50
• Reporter: Finn Nielsen
• Status: Closed
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 8.0.17
• OS: Windows (10)
• CPU Architecture: Any

[28 Jul 2019 8:09] Finn Nielsen

Description:
I get the annoying text add "could not be fetched" in Navigator SCHEMAS window.

Tables could not be fetched
Views could not be fetched
Stored Procedures could not be fetched
Functions could not be fetched

The output reports:
Error loading schema content Error Code: 1142 SELECT command denied to user '********'@'86.52.1.27' for table 'user_variables_by_thread'

When expanded the four contains all the objects for editing as usual and no real problem.

!!!!!
My host only grants me access to a single database. I don't have administrative rights for the database server.
But -
until Workbench 8.0.16 and 8.0.17 the messages was'nt there.

Host MySQL server version is 5.7.26-29-log.

How to repeat:
Connect to a server without administrative rights (i believe).

[29 Jul 2019 5:42] MySQL Verification Team

Hello Finn Nielsen,

Thank you for the report and feedback.

regards,
Umesh

[31 Jul 2019 8:12] Mike Lischke

Posted by developer:
 
This problem is caused by a non-accessible P_S and has been fixed already for the next Workbench release.

[31 Jul 2019 14:50] Christine Cole

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.18 release, and here's the changelog entry:

An inaccurate text message warned that tables, views, stored procedures,
and functions could not be fetched when a MySQL account with limited
administrative permissions on the server accessed a valid schema.

Thank you for the bug report.