I'm not the object owner, although I also don't think I'm logged in as 'theuser'. I think we have some custom setup where us developers can only use tables from 'theuser', or some-such (unsure of the details about this, I can find out from our DBAs).
The point is though, regardless of under what I'm logged in as, older versions of SQL Developer used to just insert the table name without the prefix. It must be some new feature that it also inserts the schema/user prefix, but I'd assume such a new feature would also come with an option to switch it off.
Unless it's actually a synonym, using just the object name without the schema prefix would results in an ORA- b/c the database wouldn't be able to resolve the object name. So if anything, I would treat this new feature as a bug fix, where the old behavior was 'bad.'
Now if it's actually a synonym that you have been granted, or if it's a public synonym, then we shouldn't be including the schema prefix, and from what I can tell, we're not.
all and then hit ctrl+space
SQL Dev should pop up all the public synonyms for the data dictionary SYS tables, e.g. ALL_TYPES, ALL_USERS, etc. When I select one, it doesn't prefix with SYS.
Why don't you want the schema prefix? Not sure that it matters, but just personally curious.
Ah yes the word "synonym" definitely rings a bell, I think our custom setup I was speaking of has something to do with it.
I don't see much popping up when I type "all" and then Ctrl+Space, maybe I don't have permissions for the "all" stuff.
In any case, I guess it's no big deal really - I'm just not used to having all this extra 'theuser.' cluttering my queries. And from what you tell me it really shouldn't show up, so I dunno...
What can I ask my DBA about this that may help understand the situation better?