Bug #96768 Unwanted behaviour when clicking on Tables
Submitted: 5 Sep 2019 13:07 Modified: 9 Sep 2019 12:58
Reporter: Sven Reichert Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3/8.0.17 OS:Any
Assigned to: CPU Architecture:Any
Tags: click, double-click, table, workbench

[5 Sep 2019 13:07] Sven Reichert
If you navigate through a DB and simply want to open a Table, you'll get the table name inserted to a blank query editor, or it will be inserted in an existing query for no reason which is more worse.

To deteremine that i'm not the only one who thinks that this behaviour is wrong i asked the colleagues in the dev-department and got a 10 out of 10 Response to the expected behaviour on double clicking a table name.

If you at mysql or orcale think the current behaviour is the way to go, please add an option to preferences where people can change the default behaviour to do a simple select to the table.

How to repeat:
double click on a table.

Suggested fix:
An option to set the default behaviour.
[9 Sep 2019 12:58] MySQL Verification Team
Thank you for the bug report.
[9 Sep 2019 13:28] Mike Lischke
The current behavior is focused on easy query creation. If you have to reference many tables with perhaps hard-to-type names the double click helps you to insert object names in your currently active editor, at the current cursor position.

For a quick select you can use the quick access icons that appear when you hover with the mouse over an object name, e.g. a table. The last icon (a table with a flash) is what you probably want: it opens a new tab and selects data from the table.