For now there’s no way to change the new behavior. I’ll look at it when I have time, but the new and the old editor components handle things very differently so there are going to be some differences. If the list of table names is sent as-is then “test1” would
highlight OK when standalone, but as soon as you tack a column name to it then “test1.col” will not highlight. The object names are sent so that they highlight when standalone or when typed as object_name.anything. There are many cases of highlighting that
could be more accurate if you start looking for them, but in some cases the extra work required to do so isn’t worth it. In your test1.not_a_col example Toad would have to query for column names of your table to intelligently exclude that string from the list.
That could be very costly.
On 03/05/2015 08:26 AM, Boneist wrote:
Editor not highlighting column names correctly when specified table_name.col_name
Thread created by Boneist
I have my highlighting set to display known user tables in an olive colour. However, I’ve noticed that when I refer to a table column as “existing_table.column_name”, in 12.6, the “existing_table” is displayed in olive, and the “.column_name” is displayed
in black. In 188.8.131.52, they’re both displayed as olive:
I think the 12.6 behaviour is the desired one - please can it be corrected in 12.7? Thanks.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
this post as spam/abuse.