SQL Prompt 3 SSF+[tab]

• 
  Currently there is a bug in the Query Analyzer support that stops the auto popup up of the candidate list. In the final version it will work similar to SQL Prompt 2 and popup the candidate list when it is appropriate like after a from clause. The sinppets work in a slightly different way in this version. They are in the candidate list so if you press ctrl + space and then select a snippet and press enter it should be inserted. If you prefer the old way then please tell us and explain why. The query analyzer support is still in the early stages but all this will be ironed out by the final release.
  
  Lionel

  Lionel September 04, 2006 11:51

  - 0 +
• 
  There are no snippets that start with s. Where is the "select * from " snippet? The list only contains "acud" down to "cuni".
  
  For the snippets to be efficient, the key combos necessary to generate them need to be much shorter than the text themselves.
  
  SQLP2's "ssf" was efficient.
  
  The SQLP3 key combos appear to be less efficient:
  "ata" [crtl] + [space] + [crtl] + [R arrow] + [enter]

  HotAir September 05, 2006 08:35

  - 0 +
• 

  HotAir wrote:

  There are no snippets that start with s. Where is the "select * from " snippet? The list only contains "acud" down to "cuni".
  
  For the snippets to be efficient, the key combos necessary to generate them need to be much shorter than the text themselves.
  
  SQLP2's "ssf" was efficient.
  
  The SQLP3 key combos appear to be less efficient:
  "ata" [crtl] + [space] + [crtl] + [R arrow] + [enter]

  
  The most effient way to insert a snippet is to start by pressing CTRL + SPACE and then type the snippet. So your example above would be:
  
  CTRL + SPACE + "ata" + ENTER
  
  In fact, with that specific example you cite, you needn't type the whole snippet name as it's selected near the top of the list.
  
  Hope that helps,
  
  
  
  Dom

  Dominick Reed September 05, 2006 08:45

  - 0 +
• 
  I used "ATA" in my example because "SSF" in nowhere to be found.
  
  Is this a defect or part of the beta that the candidates for snippets only contains up to "cuni"?
  
  Thanks for the usage tip; I'm conditioned by how I use Visual Studio and I've always considered intellisense a completion tool "<type something>, now complete it" as opposed to "I want to complete what I type next, <type something>".

  HotAir September 05, 2006 08:57

  - 0 +
• 

  HotAir wrote:

  I used "ATA" in my example because "SSF" in nowhere to be found.
  
  Is this a defect or part of the beta that the candidates for snippets only contains up to "cuni"?
  
  Thanks for the usage tip; I'm conditioned by how I use Visual Studio and I've always considered intellisense a completion tool "<type something>, now complete it" as opposed to "I want to complete what I type next, <type something>".

  
  Only going up to Cuni is just a limitation of the snippets included with the beta, so yes, ssf would be in there for the final release.
  
  Snippets should work both ways, hopefully. What we hope to be able to accommodate is both insertion by browsing, and insertion by completion. When you get to have a large number of snippets, chances are you're not going to remember all of them, so being able to browse a list is important - especially for infrequently used ones. This is facilitated by the CTRL + SPACE to browse a list.
  
  Working the other way, typing "ata" should probably insert the snippet just in itself, but it could potentially lead to a few mistakes. Typing "ata" then pressing CTRL + SPACE should at the very least drop you onto the snippet in question and I thnk it's a bug that it doesn't do this.
  
  leave it with us.
  
  :-)
  
  Dom

  Dominick Reed September 05, 2006 09:43

  - 0 +
• 
  In SMS, typing ata and then pausing does show the corresponding snippets in the All Common Objects category. I can then press ENTER to auto-complete.
  
  So, I type ata + ENTER. You can still type ata + TAB, if you set TAB as a completion key in the SQL Prompt Options dialog.
  
  I have spotted an intermittent bug where the candidate list does not always show snippets when you start typing. I've logged it in our bug tracking system.

  KirstyBurgess September 06, 2006 07:03

  - 0 +
• 
  much nicer than SQL prompt 2.0
  
  it will be nice to intergrate SQL refactor into SQL prompt 3.0
  
  that would make a very nice program

  ljk September 06, 2006 09:20

  - 0 +

Add comment

Please sign in to leave a comment.