Comments
5 comments
-
Have you tried switching to the snippets only list, using Ctrl + Left Arrow?
Tilman -
Yes, just trying to make the tool more friendly/customized to the user's work habits.
In the case of the "re" snippet - the number of "re%" items in the list is shockingly high. If I type just "re" on a new line, I get a whole bunch of reserved words and CRUD SP's (for tables beginning with Re) - 32 items in this case. It's worse when there's other code on the line...
Just typing "s" gives over 190 items in the candidates and my 5 "s" snippets are at the very end of the list. If you think about it, the frequency of use of snippets is much more likely to be higher than, for instance, needing a user as in "srobinson" as a candidate - hence placing snippets at the top is more efficient and useful than burying them at the bottom of the candidates list (which, as you know, is the most used and initially presented list). Productivity/efficiency are the key criteria - having to Ctrl+Left to get to snippets every time isn't exactly fitting...
Please consider as an enhancement my original suggestion to enable the user to determine the item type sequencing - it could prove a useful enhancement to many constituents. -
You've got a valid point and i've added a suggestion to our list. Customizing the CL in the way you described is going to be tricky, though, as currently it displays different things depending on where you are in your script.
Another user has also suggested to bring back the v2 functionality that allowed you to replace snippets without opening the CL. How do you feel about that?
Regards,
Tilman -
Given the delay between keystokes determines whether the CL pops up or not and given that we may well know the mnemonics of our most-frequently-used snippets, that could be a viable solution. Prompt SQL used {tab} as the completion character; I couldn't even run 2.x so it may differ, but if {mnemonic}{tab} can auto-complete the snippet, I'd vote for that.
Thanks for taking all our feedback so seriously and considering alternatives. -
And that is very much the problem with intellisense type functionality for a relational database. The number of objects in scope at any one time, versus the number you'd expect to see in C#, Java, or C++ is often an order of magnitude larger when dealing with a database. It's a pain. Now I'll admit that not all of those reserved words are relevant all of the time, and we'll definitely refine that list based on context with future versions, but unless you want to wait until the middle of next year for the final release....
Add comment
Please sign in to leave a comment.
Yes, I could NOT use "re" as the mnemonic, but if there was an option to show snippets first, or better still, allow us to define the sequence that we want for ALL object types, as in:
That would be super-flexible...