Weird case of auto-completed items

[a_kassabian]

I am working in an Oracle Apps schema. I have found that, sometimes, the auto-completed items are pasted in upper case and sometimes (actually, most times) in lower case. Since Oracle is case-insensitive and I have my editor preference set to no alter the case of keywords, what is causing this behavior?

 

[Marco Kalter]

This depends on the "Coding Style" preference setting on the "Code Assistant" preference page. If the "Use original case if possible" option is enabled, the style from the source of the referenced object is used, if available.

 

[a_kassabian]

But all dictionary views in Oracle are upper case. How would you recover the case of an object, then?

 

[Marco Kalter]

For program units and views it inspects the source in the dictionary. For tables there is no source, and the dictionary indeed reports everything in uppercase.

 

[a_kassabian]

In that case, why is it that some view members are auto-completed in upper case and some in lower case?

 

[Marco Kalter]

I assume that they are defined as such in the source? If not, please send me an example view definition that exposes this problem.

 

[a_kassabian]

Oh, I see. So the auto-complete does not look in the dictionary tables for views. It looks at the actual query text. That explains why it takes longer to auto-complete view members.

It seems to make more sense to autocomplete view members in the editor's case too since, from a programmer's point-of-view, they are "the same" as tables. Don't know how others feel about it.

Anyway, this answers my question.