SQL Prompt 7.1 Beta (now closed)

• 
  Hello,
  
  it seems that download file was not updated to 7.1.0.112.
  
  Best regards,
  
  Klaus

  kondrich October 21, 2015 01:52

  - 0 +
• 
  Hi Klaus,
  
  Thank you for finding this!
  
  I've updated the zip file with the new release.
  
  Best regards,
  
  David

  David Priddle October 21, 2015 05:29

  - 0 +
• 
  Hi David,
  
  thank you for updating the file.
  
  Best regards,
  
  Klaus

  kondrich October 21, 2015 06:54

  - 0 +
• 
  Hi,
  bad formatting (FOR XML PATH):
  

  SELECT  @MissingProducts = STUFF(
  										  (SELECT   N', '
                                                      + CAST(Id AS VARCHAR(30))
                                             FROM     @ProductsWithPrices p
                                             WHERE    NOT EXISTS ( SELECT
                                                                *
                                                                FROM
                                                                dbo.Product pp
                                                                WHERE
                                                                pp.Article = p.Id )
                  FOR                      XML PATH('') ,
                                               TYPE).value('text()[1]',
                                                           'nvarchar(max)'), 1,
                                           2, N'');
  

  sdks November 05, 2015 14:24

  - 0 +
• 
  Hi sdks,
  
  If you could put this and any other formatting suggestions you have in our formatting survey, that would be great.
  
  We're working on upgrading the formatter so that it is more powerful and flexible, so having your suggestions would help a lot.
  
  Best regards,
  
  David

  David Priddle November 06, 2015 04:49

  - 0 +
• 
  Done. Another bug with GROUP BY suggestions. When auto-completing non aggregate columns it did not include "s.dir" :
  

  SELECT  ProductId ,
                          COUNT(*) * s.dir AS Qty ,
                          NULL AS LocationId
                  FROM    dbo.SalesOrder_Product
                          CROSS APPLY ( SELECT    [dbo].[fn_SalesOrderProductQtyChangeSignUnit](@PreviousStatusCode,
                                                                @OrderStatusCode) AS dir
                                      ) s
                  WHERE   SalesOrderId = @SalesOrderId
                          AND s.dir IS NOT NULL
  				GROUP BY ProductId
  

  (120,1): SQL72014: .Net SqlClient Data Provider: Msg 8120, Level 16, State 1, Procedure p_UpdateSalesOrderStatus, Line 28 Column 's.dir' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.
  

  
  

  David Priddle wrote:

  Hi sdks,
  
  If you could put this and any other formatting suggestions you have in our formatting survey, that would be great.
  
  We're working on upgrading the formatter so that it is more powerful and flexible, so having your suggestions would help a lot.
  
  Best regards,
  
  David

  sdks November 07, 2015 04:09

  - 0 +
• 
  Hi sdks,
  
  Thanks for identifying this! I can reproduce it and am working on a fix now.
  
  Best regards,
  
  David

  David Priddle November 09, 2015 08:40

  - 0 +
• 
  Another bug. SHIFT+F5 does not work then there are syntax errors in the window. For example:

  SELECT 1
  SELECT * FROM
  

  
  If I just highlight "SELECT 1" I can execute it. However when the cursor is somewhere between "SELECT 1" statement and hit SHIFT+F5 it gives following error:
  

  ---------------------------
  SQL Prompt - Execute current statement
  ---------------------------
  SQL Prompt was unable to complete this operation.
  
  Problem areas have been highlighted.
  ---------------------------
  OK   
  ---------------------------
  

  sdks December 04, 2015 08:04

  - 0 +
• 
  Hi sdks,
  
  This is what we'd expect to see. If there's an error in the current batch then "Execute current statement" will display an error rather than potentially execute too much or too little (which would be pretty risky).
  
  If you place a "GO" batch separator between the error and the statement you're working on it should be able to accurately execute the current statement for you.
  
  Thanks,
  Aaron.

  Aaron L December 07, 2015 06:42

  - 0 +
• 
  There is a bug in highlighting selected variable. Take the following query for example
  

  DECLARE @theXml XML = '<a>b</a>'
  SELECT t.node.value('.', 'VARCHAR') FROM @theXml.nodes('/') AS t(node)
  

  
  After clicking on the variable name in the declare line, same variable in not highlighted on the second line.

  stanac December 10, 2015 02:24

  - 0 +
• 
  Thanks stanac - the highlight matching objects experimental feature is still under development and we've still got a few more objects/statements that we need to "hook up" to get them highlighting correctly. We'll look into getting this one fixed.

  Aaron L December 10, 2015 05:59

  - 0 +

Add comment

Please sign in to leave a comment.