Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
No support autocomplete/intellisense for table aliases?

I was excited for this plugin to work, as it would be nice to stay within visual studio code and not switch into Datagrip or SQL Developer all the time. But the very first, very basic query I tried seems to have flummoxed the intellisense.
Here's the simplest example that will illustrate the problem. In this example, after I type "t." in the where clause, intellisense should be suggesting a list of all the columns in MY_TABLE. Instead it's not suggesting anything.
SELECT * FROM MY_TABLE t WHERE t.
Answers
-
Hi and thanks for the feedback!
We are adding support for table/view aliases with IntelliSense in the next release (version 21.4). I will try to remember to ping you on this thread when it is released.
(Also, that release will also have immensely improved autocomplete in many other ways - it should be a huge step forward).
-
I'll keep an eye out for the next release, thanks. I'm glad to hear this tool is still under active development and will be getting more features.
-
It's not working.
-
Hi, we can reproduce this bug and it should be fixed in the next release. Sorry about that.
-
Thank you. 👍️ When will be released the next version?