How can we help you today? How can we help you today?

Show SP parameter types incompatible with leading comma

When both of these options are enabled:
  • Inserted Code -> Objects & Statements -> EXEC Statements -> Show parameter data types
  • Format -> Commas & parentheses -> Commas in multiple-line statements -> Place commas at start
the output is hard to read, tedious to edit, and wasteful of space. SQL Prompt 5.3 did this the same way. 
EXEC testproc2
   @parm1 = NULL
 , -- bit
   @parm2 = NULL
 , -- bit
   @parm3 = NULL
 -- bit
This might work better if the parameter types were inserted as block comments and before the comma instead of inline and after.
EXEC testproc2
   @parm1 = NULL /* bit */
 , @parm2 = NULL /* bit */
 , @parm3 = NULL /* bit */
The effect on the trailing-comma case would be minimal. 
EXEC testproc2
   @parm1 = NULL /* bit */,
   @parm2 = NULL /* bit */,
   @parm3 = NULL /* bit */


--
SQL Prompt 6.0.0.411 in SSMS 2012 (11.0.3128.0)
ewhipple
0

Comments

1 comment

Sort by
  • Brian Donahue
    Hi,

    Thanks for your input, but we can't track requests for changes to SQL Prompt using the facilities of this forum software. Hate to make you repeat yourself, but could you add this to the uservoice page?

    http://redgate.uservoice.com/forums/944 ... uggestions

    This makes it easy to manage, track, and upvote requests for changes.

    Thanks!
    Brian Donahue
    0

Add comment

Please sign in to leave a comment.