This content has been marked as final. Show 6 replies
It should be dynamically resized to accomodate the longer strings. That's a bug and will get fixed.
I don't see that behavior in 3.2.1, even for a <schema.file> size of <6.30>. Perhaps your schema name is longer? Generally if you type the schema name in the worksheet, the schema name appears in the pop-up. Not typing it can still produce schema prefixes in the list, but only if the algorithm finds a reference to that file/view prefix in a different schema. There is no preference controlling that.
Actually, I do recall a width issue in some earlier release. It was fixed but I cannot quickly locate any bug or forum reference to it at this time. In your case, does it depend on the screen resolution setting or the size of the SQL Developer application window?
I recall another slightly different issue in 3.1:
3.1 Prod : Code Completion window is too large
that was resolved by this fix in 3.2.x:
Bug 14528188 - FORUM - CODE INSIGHT LIST EXTENDS OUTSIDE OF SCREEN WHEN HEIGHT LESS THAN 1024
SQL Developer Team
The popup width is 1/4 of screen width. Is your display narrower than 1920?
If your schema is the same as object owner, the popup shouldn't prefix names with schema.
Finally, the mouse over suggested item pops up tooltip with full name. This is how you can identify full queries from SQL History. For example if you have recently executed something like this:
select * from user_objects where object_type = 'procedure';
then long queries are truncated in insight and you only see something like this:
select * from user_objects where object_type =
Mouse over this entry reveals the full query.
Thanks for the feedback.
My screen resolution is 1280x800
In SQL Worksheet I connect as "my_user" but I am querying a different schema "warehouse".
Now I look closer the contents of the popup when I press ctrl+space on a table name actually contains:
Where the first schema name is in "grey" and the second schema name and table_name is in black bold.
Extra schema prefix seems to be a bug. I just doublechecked that it has been fixed in the next patch: connected as scott I see all of the following
select * from em<ctrl-space>
select * from hr.<ctrl-space>
select * from hr.e<ctrl-space>
prompt hr.employees correctly.
Thanks for that.