Discussions
Categories
- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.7K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.3K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 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
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 466 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Completion Insight changes in 22.2?

In previous version I was able to type in 'SELECT p. ' (where p is my table alias) and see the columns in my table. I'm now seeing what appears to be a list of schemas/users. Am I doing something wrong or did something change?
Update: If the table is in my current schema, it works as it always has. If I'm using a synonym to a table in another schema, it appears that the completion insight might not be working as I expected. Can somebody else try this and confirm?
Answers
-
Yes, I observed the same thing. I didn't notice that it still works with own tables, since most of our tables are accessed via synonyms. Even qualifying the table name with user name does not help.
-
Can you provide an example? My 22.2 rig
-
Well, actually I cannot reproduce that right now. But when I have another big SQL of, say 117 lines in the worksheet above my actual SQL, I get columns proposed that do not belong to the table for which I try to enter my new SQL.
I did not find out yet, which the exact conditions are but have a look at this:
Here, the "*" is offered only when the above SQL exists. The is something strange going on with the parsing.
And then that here:
Here columns of the inner SQL above are offered: gp_nr and gp_nr_betrieb are not part of wt_funktion.
I'm having no demo schemas installed, so I hope you can reproduce something like this.
Kind regards,
Lothar
-
It's quite possible something is up with the parser. But I'll need a test case.
-
Okay, here you are:
I disabled the autopopup and called that via CTRL-Space.
-
In your example 't' isn't an alias for your table.
This works
Contents of my editos
select * from (select * from user_tab_colums) c; select t. from user_tables t;
-
Yes, you are right, but adding the alias does not help in my case:
The list is influenced by the SQL above. If I remove that, SQL Developer shows a different one without column_name:
Also the list in this case it ordered differently each time, I call it:
IIRC the column list used to be ordered alphabetically.
Regards,
Lothar
-
there's for sure a bug here if not two. For the moment i can only verify the sorting/alpha issue. I'll log that now.
-
I have been trying to create a consistent test case, but the issue is not consistent. It definitely only happens (at least for me) when I am using synonyms to tables in another schema. If I fully qualify the schema.tablename in my SQL it works fine.
-
I would say that the Completion Insight function does not work at all without table schema in 22.2.