First impression and a few bugs

• 
  INFORMATION_SCHEMA does not appear in the list after 'SELECT * FROM'. That one is a requisite for me since a lot of information can be pulled out of it.
  
  Keep up the good work!

  bert September 02, 2006 10:52

  - 0 +
• 

  bert wrote:

  When I use SQL Prompt I like to have full intellisense on the table columns. Therefore, I first type in 'SELECT FROM Table t' and afterwards I fill in the columns. When I type in 't.' on the point SQL Prompt selects the first item it has with T. This problem is bound to autocomplete on '.', therewith imho degraded to a useless function :lol: .

  
  This is definatly a bug and will be fixed for the final release. To make this easier we are going to add a column picker that will alow you to select from list of relevent columns.
  

  bert wrote:

  When I join another table (INNER JOIN) I would like to have a table list, but the also is a column list. Since I do not join on columns ...

  
  Sorry that is another bug again.
  

  bert wrote:

  SQL Prompt seems not to understand CTE's (Common Table Expressions). Since these imho are a great new feature in SQL Server 2005, I would like to have intellisense support on them.

  
  It does not understand CTEs at the moment but we are looking at adding support for them in the final version.
  

  bert wrote:

  The autocomplete on space seems a little bit frustrating to me (though I found out it is possible to disable it). When SQL Prompt pops up during a 'SELECT ' action, I would like to be enabled to type on, not expecting a column name and the complete from clause. I would definitely prefer the TAB key, as it is in Visual Studio intellisense.

  
  I find the space a little frustrating as well which is why there is an option to disable it .
  

  bert wrote:

  About the TAB completion: when I use TAB to complete a word, the TAB is not cancelled, so I bump away from what I typed in. Visual Studio just cancels the real TAB and I should like it that way either...

  
  This will be fixed in the final release.
  

  bert wrote:

  Another point of interest is when I type in 'SELECT * FROM Table' where I let SQL Prompt do the Table part ('Table AS t') I would expect the '*' to be prefixed as 't.*'. Should not be really impossible whenever there is just one * and no other table names.

  
  That is and interesting sugestion. I will add it to our list of suggested features.
  

  bert wrote:

  Declaring a variable seems not to be supported in SQL Prompt. When I declare 'DECLARE @... NVARCHAR(MAX)' I should expect SQL Prompt to help me. Setting some string in a variable also does not work.

  
  We only have basic support for SELECT, INSERT and UPDATE statments atm but we are working on expanding this dramatically by the final release.
  

  bert wrote:

  Also, when designing a query in a string, SQL Prompt is not a pleasing tool to keep me company. Since it only produces dull information, just try to detect whether or not in a string and therewith disable SQL Prompt help.

  
  This is actually a bug it shouldn't give you any intelisense. The reason that the information is not very useful is it doesn't know what to do so pops up in a default mode.
  

  bert wrote:

  Well, that's enough by me for this weekend. Next week I will test on with SQL Prompt and give you some more ...

  
  Thanks a lot I really apreciate all the feedback.
  

  bert wrote:

  INFORMATION_SCHEMA does not appear in the list after 'SELECT * FROM'. That one is a requisite for me since a lot of information can be pulled out of it.

  I have added this to our list of sugested features.
  
  
  Lionel

  Lionel September 04, 2006 14:52

  - 0 +

Add comment

Please sign in to leave a comment.