Comments
4 comments
-
Hi Janelle,
Thanks for posting. The reason why '.' inserts the selection is, because the dot is used to qualify table/column/etc. names, as e.g. in 'dbo.table.column'. If somebody wants to enter the above using SQL Prompt, they can select 'dbo' from the candidate list, press '.' to enter it and then the candidate list will open again immediately with all the objects that belong to 'dbo'. They can then select 'table', press '.'... And so on.
I'm not quite sure what your problem is, do you have identifiers that contain dots?
SQL Prompt 3 will allow much more configuration of the keyboard settings so hopefully that will solve your problem.
Regards,
Tilman -
The problem isn't that aliases contain dots - it's that SQL Prompt needs to understand that aliases exist. This could be done by parsing the From clause of the query as written so far and adding aliases to the candidate list.
I suppose for completeness, column aliases could be treated the same way. -
I just ran into this using aliases for something like:
select * from foo f where f.
and there were other table names that start with f, so it completed the first one. Funny thing, f.column_name was lower in the list.
Maybe SQL Prompt should sort those to the top or recognize the use of an alias and not perform completion, but instead perform another suggestion after hitting "."
Patrick -
Ah, I see what the problem is. SQL Prompt 3 will support aliases, which will solve this problem.
Regards,
Tilman
Add comment
Please sign in to leave a comment.
I frequently use sysnonyms, so I often have to go back, deleting the incorrect 'intellisensed' name, and then re-type what I did want!
:?