SQL Prompt attempts to offer suggestions within Comments

• 
  Maybe a hot-key to turn off the automatic suggestions? Like ctrl-space will always bring up a list maybe another combination can turn it to "manual" instead of on a delay for when typing comments.

  JTShyman December 13, 2006 14:27

  - 0 +
• 
  The Hot Key idea would work, but this program is so smart, I would hope it could tell it was between /* */ or after a -- on a line and stop suggesting. I don't recall this issue with version 2; I only remember it capitalizing key words as I typed within a comments section, which I generally wanted it to do most of the time anyway.

  dldlcd December 13, 2006 15:13

  - 0 +
• 
  Hi,
  
  Thanks for posting.

  SQL Prompt needs to keep from offering any suggestions of any kind, when I am typing comments in my code. It is higly annoying.

  We are aware that SQL Prompt is not very good at detecting comments. We hope to fix this in a future version. On the other hand, after the first beta, some people told us they want Prompt in comments, as they write SQL in comments. If they want to run it they highlight the necessary bits.
  
  (A temporary solution might be turn off automatic pop ups via the options dialog.)
  

  Maybe a hot-key to turn off the automatic suggestions? Like ctrl-space will always bring up a list maybe another combination can turn it to "manual" instead of on a delay for when typing comments.

  I've added a suggestion to our list.
  
  Regards,
  
  Tilman

  Tilman December 18, 2006 06:40

  - 0 +
• 
  There will be differences of opinion, which I understand. But, it would seem to me that you do not want suggestions in a comment section - we're typing verbage to describe the code to make it easier to understand what the SQL Object actually does and how; not trying to type literal SQL code. The idea of a whole select statement in the description is overkill; Pseudo-code is more realistic or even a Technical Specification Document. But, this is a debate that doesn't belong here.
  
  My main point is that if I'm spending a good deal of money on a software product to make my programming easier, I do not want to have to Hot-Key or click-here-and-there just to make the software stop doing something and then click-here-and-there to make it work again; this software was supposed to make my job easier. I don't want to stop in mid thought and focus to turn off and then back on an ability for the software to do its job; that's counterproductive.

  dldlcd December 18, 2006 09:57

  - 0 +
• 
  Comments are an interesting question... but what about strings / dynamic SQL? If this works:
  
  /*
  SELECT * FROM hum
  */
  
  (brings up HumanResources in the AW database)
  
  ... then why shouldn't this work:
  
  ---
  DECLARE @... VARCHAR(MAX)
  
  SET @... = 'select * from hum'
  ---
  
  I personally don't type a lot of SQL in comments, but I do a fairly large amount of work with dynamic SQL.

  amachanic December 18, 2006 14:43

  - 0 +
• 
  Hi,
  

  My main point is that if I'm spending a good deal of money on a software product to make my programming easier, I do not want to have to Hot-Key or click-here-and-there just to make the software stop doing something and then click-here-and-there to make it work again; this software was supposed to make my job easier. I don't want to stop in mid thought and focus to turn off and then back on an ability for the software to do its job; that's counterproductive.

  You are right. As mentioned earlier, this is something we are trying to fix. See this thread for another discussion
  
  http://www.red-gate.com/MessageBoard/vi ... php?t=3923

  Comments are an interesting question... but what about strings / dynamic SQL? If this works:
  
  /*
  SELECT * FROM hum
  */
  
  (brings up HumanResources in the AW database)
  
  ... then why shouldn't this work:
  
  ---
  DECLARE @... VARCHAR(MAX)
  
  SET @... = 'select * from hum'
  ---
  
  I personally don't type a lot of SQL in comments, but I do a fairly large amount of work with dynamic SQL.

  Again, it shouldn't work in comments. I suppose if it did work in string literals somebody else wouldn't like it. Sounds like it should be an option in both cases...
  
  Regards,
  
  Tilman

  Tilman December 19, 2006 08:19

  - 0 +

Add comment

Please sign in to leave a comment.