Current Observations/Problems/Quirks

• 
  Hi,
  
  Thanks for posting.
  

  V2 did not require data types (such as int, varchar, etc.) to be uppercased when keywords are. It would be nice to have the option not to, since the standards here require that the data types be lower case, but the keywords be in upper case.

  An intellisense box doesn't seem to make sense after a DECLARE statement

  Could you explain a bit more what is happening and what you would expect? (We have already fixed a bug where it didn't show data types.)

  Only the last variable seems to be appearing in the intellisense box when declaring multiple variables.

  I've added it to the list.
  

  It adds a second single quote all the time I type one, not just when starting a quoted string. For example, if I have the code "SET @... = '", and then I type "Y'", it automatically puts an extra "'" so it looks like "SET @... = 'Y''", instead of "SET @... = 'Y'".

  I'm afraid that is by design.
  

  The intellisense box seems like it should go away if there are no options. For example, if I declare a variable @x int, and then type "SET @x = 123", the box intellisense box is there with no options. I then have to hit <enter> two times to move to the next line.

  I think there are 2 things going on here a) the candidate list stays open, so you can use backspace and change the filter, b) when the candidate list is empty, pressing Enter should close it and insert a new line, rather than just close it.
  

  With autocomplete for the single quote turned on, when I type "SET @y = 'abc", a single quote is added to the end. I must press <end>, then <enter> to go to the next line instead of just <enter>, or the single quote that was added is moved to the next line. I don't know what can be done about it, but it makes the feature less desirable to use.

  I'm afraid this is also part of the current design. I agree that this feature could take some improving.
  

  With autocomplete for the single quote turned on, sometimes after typing a single quote it would get into an endless loop adding quotes, and I would have to kill the process to get control back (MSSMS locks up). For example, typing "DECLARE @x char(3); SET @x = '" would become "DECLARE @x char(3); SET @x = '''''''''''''''''''''''''''''''''''''''''''''''''...", and would not stop adding single quotes. This does not happen all the time, and I haven't figured out what is causing it exactly. I have learned to save often, and turn off the single quote option if it happens more than twice on a given script I am editing. Come to think of it, it seems to happen when I have the window split in MSSMS.

  Please let us know if you can reproduce this reliably. We thought we had it fixed.
  

  It would be nice to be able to configure the spacing, comma location, etc. when parameters and data types are added for stored procedures and functions. We put the comma in front instead of at the end, so I have to redo the parameters list everytime I do it

  I've added it to our list.

  When using the automatic adding of all the columns for a table when pressing <tab> on the "*" in a string of "SELECT * from my_table", is there a way to set the format of it? In V1, we could move the commas to the beginning of the columns if we wanted to do so. Otherwise I have to edit the list each time.

  Already on the list.

  Editing code is sluggish in large stored procedures

  Also a know issue. Would you mind, though, sending us an example? You can pm it to me if you don't want to publish it here.
  

  Sometimes keywords (such as usages of "to", "for", etc.) in comments are being capitalized when typing in stored procedures

  I'm afraid we are having some problems determining when Prompt is in a comment.
  
  Regards,
  
  Tilman

  Tilman December 13, 2006 12:02

  - 0 +
• 
  Thanks for responding so quickly. I followed up to a couple of your replies below.
  

  V2 did not require data types (such as int, varchar, etc.) to be uppercased when keywords are. It would be nice to have the option not to, since the standards here require that the data types be lower case, but the keywords be in upper case.

  An intellisense box doesn't seem to make sense after a DECLARE statement

  Could you explain a bit more what is happening and what you would expect? (We have already fixed a bug where it didn't show data types.)

  
  One example of my statement regarding data types is when I type "declare @x int", V2 changed it to "DECLARE @x int", but V3 changes it to "DECLARE @x INT".
  
  In regards to the DECLARE statement, when I type "DECLARE ", I am getting an intellisense box, when it doesn't seem like I should be. I may be spacing out, but isn't the only thing allowed after a DECLARE keyword a new variable, cursor, etc. name?
  

  With autocomplete for the single quote turned on, sometimes after typing a single quote it would get into an endless loop adding quotes, and I would have to kill the process to get control back (MSSMS locks up). For example, typing "DECLARE @x char(3); SET @x = '" would become "DECLARE @x char(3); SET @x = '''''''''''''''''''''''''''''''''''''''''''''''''...", and would not stop adding single quotes. This does not happen all the time, and I haven't figured out what is causing it exactly. I have learned to save often, and turn off the single quote option if it happens more than twice on a given script I am editing. Come to think of it, it seems to happen when I have the window split in MSSMS.

  Please let us know if you can reproduce this reliably. We thought we had it fixed.

  
  The way to reproduce this is to open up a new window in MSSMS, split the window in two using the splitter, then type the following: "declare @x char(1);set @x = '". Doing that will cause the error every time. The split window seems to the cause of it.

  Matthew.Wilkerson December 13, 2006 15:18

  - 0 +

Add comment

Please sign in to leave a comment.