Bug #101280 | Auto complete only works for reserved names. Table names and columns do not | ||
---|---|---|---|
Submitted: | 22 Oct 2020 21:35 | Modified: | 22 Oct 2020 22:18 |
Reporter: | Tiago Link | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 8.0.22 | OS: | Windows (Windows 10) |
Assigned to: | CPU Architecture: | Any | |
Tags: | auto-complete, auto-completion, columns not auto completing |
[22 Oct 2020 21:35]
Tiago Link
[22 Oct 2020 22:15]
MySQL Verification Team
Works
Attachment: 101280_1.png (image/png, text), 87.13 KiB.
[22 Oct 2020 22:16]
MySQL Verification Team
Wrks
Attachment: 101280_2.png (image/png, text), 68.40 KiB.
[22 Oct 2020 22:18]
MySQL Verification Team
Thank you for the bug report. Please see screenshots.
[23 Oct 2020 2:13]
Brian Plunkett
AutoCompletion Error from "Sele..." not completing keyword "SELECT"
Attachment: AutoCompletionError.png (image/png, text), 2.55 KiB.
[23 Oct 2020 2:31]
Brian Plunkett
MySQL Community: Tiago Link is correct in that there are intermittent caching issues with the member list for the autocompletion code. This is happening for multiple reasons, the primary being that once the AutoCompletion code encounters an error in the SQLEditor pane while the "Automatically Start Code Completion" setting is enabled, the code continues to have completion errors. This might be due to a race condition within the user interface and/or window management system. One thing I've determined, the completion code fails less if/when the table has been added to the statement before trying to process for column names. An example would be "SELECT * FROM table" then, going back and editing the wildcard. Whether a default database was selected or not, the problem presents itself the same way. I've consistently had the error while trying to type simply "SELECT * FROM information_schema.COLUMNS". Suggested workaround: Use the Snippets to populate most of the statement(s) into the SQLEditor, and then edit the specific areas of the statement to reduce any errors which might be occurring from an event firing (and possibly failing) on each character typed. You'll be happier if you type less!