Intellisense does not work with synonyms

[Helene]

The use of intellisense is very helpful, but unfortunatly it does not work when you use synonyms. Could you please fix this? I consider this to be a bug, and a quite annoying one.

with regards Helene

 

[Marco Kalter]

Synonyms should work just fine. For example, if you type "dbms_o", it should suggest dbms_output (which is a public synonym). If you type "dbms_output.", it should list all dbms_output package elements. Can you confirm?

 

[Helene]

That is not quite what I mean.

If I create a synonym myschema.mysynonym for a table myschema.mytable, and I start typing mySchema.Mys pl/SQL Developer is not able to "suggest" mySchema.MySynonym.

F6 does not work as expected either. It appears as though there is no object starting with "Myschema.mys", or something else is selected if there is another ordinary object: e.g. myschema.mysecondtable.

If I type mySchema.MySynonym, then the columns of the table are suggested as expected.

 

[Marco Kalter]

Synonyms are indeed not included when typing the schema name. If you only type part of the synonym name (in this case for example MYS), without the schema prefix, the synonym should show up in the list.

 

[NickC]

What about Non-Public Synonyms in a different schema, but with which you have rights?

For our example, we have a table FACT_CLAIM, originally in DW.FACT_CLAIM, but now we have a synonym in it's place which points to another schema (DWLOAD1.FACT_CLAIM)

When I type 'DW.FACT_' I don't see either of the FACT tables that have synonyms for that schema.

But if I run 'Select * from DW.FACT_CLAIM', of course I can use/see the table.

 

[Marco Kalter]

Private Synonyms in another schema will not be picked up by the Code Assistant. It is limited to the object types listed in the preferences.

 

[Helene]

Will you fix this? This is really very annoying.

 

[Marco Kalter]

I have added this to the list of enhancement requests.

 

[Terence]

hi marco, was this ever resolved?
thanks