Bug #73805 autocomplete in editor not working for tables and fields
| Submitted: | 4 Sep 2014 13:37 | Modified: | 6 Sep 2014 6:52 |
|---|---|---|---|
| Reporter: | austin woz | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 6.2.1 | OS: | MacOS |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | auto complete, autocomplete | ||
[4 Sep 2014 13:37]
austin woz
[4 Sep 2014 14:37]
MySQL Verification Team
autocomplete working
Attachment: auto_complete.png (image/png, text), 111.93 KiB.
[4 Sep 2014 14:40]
MySQL Verification Team
Thank you for the bug report. I couldn't repeat on below environment: MySQL Workbench Community (GPL) for Mac OS X version 6.2.1 revision 12170 build 2094 (32 bit) Configuration Directory: /Users/miguel/Library/Application Support/MySQL/Workbench Data Directory: /Volumes/MySQL Workbench/MySQLWorkbench.app/Contents/Resources Cairo Version: 1.10.2 OS: OS X 10.9.x Mavericks CPU: 4x Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 16.00GiB RAM
[4 Sep 2014 18:03]
austin woz
To repeat try entering in a table name, or a field name, this does not work. Auto complete works for mysql commands as you have established. So Auto complete is not working for table or field names
[4 Sep 2014 18:05]
MySQL Verification Team
Thank you for the feedback. I will try it.
[4 Sep 2014 18:19]
MySQL Verification Team
Thank you for the bug report. Changed synopsis to reflect the actual issue.
[4 Sep 2014 18:50]
Alfredo Kojima
Posted by developer: This was fixed in 6.2.2
[6 Sep 2014 6:52]
austin woz
confirmed thsi is fixed in 6.2.2
[5 Nov 2014 3:40]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.2.2 release, and here's the changelog entry: On OS X, the SQL auto-completion feature did not function for table or field names. Thank you for the bug report.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.071 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.