Comments
2 comments
-
Here's a another instance that just occurred equally annoying.
I'm trying to enter the following line in SSMS:
GRANT EXECUTE ON [insertduckreturneditemsv41] TO webserver
I type in:
GRANT EXECUTE ON [insertduckreturneditemsv41]
at which point SQL Prompt pops up its windows trying to show me the possible choices, the first stored procedure it shows is a completely different one.
When a press the space key at the end of the above (right after the desired stored procedure name that i had typed in), SQL Prompt appends the name of the other stored procedure and I end up with:
grant execute on [insertduckreturneditemsv41][dbo].[accountpoolcleanupgetallreserved]
which is of course wrong. I must then go in and manually delete what SQL Prompt added.
thx.
r- -
Sounds like you'd need to disable the SPACE and ENTER auto-completions in the options, and use another key to signify you want to accept what is highlighted, when you do want to do so.
Add comment
Please sign in to leave a comment.
Here's the scenario. it happens semi-frequently but this is one example.
In SSMS, i'm editing a stored procedure.
At the end I type in GO intending to have the command "GO" on a blank line.
As I type go, SQL Prompt pops up a box trying to auto-complete what I am typing which is fine. The only choice it shows in its list is "GOTO".
So I type GO and then hit enter because i want the command GO on a blank line.
When I type enter, SQL Prompt changes GO to say GOTO and now i have of course an error because this is not what i want.
I think the issue is that SQL Prompt is using the Enter key to mean select something from its list.
In Visual Studio, intellisense/autocomplete works a bit differently and these issues don't occur.
Any way to have SQL Prompt work the same way so this problem doesn't keep happening?
thx
r-