173 results found
-
Do not consider code flagged for no formatting when formatting.
If I have a very large script with the majority of it with formatting disabled, or even with just a highlighted small area... the ctrl-K,ctrl-Y formatting seems to consider the parts it will not be formatting. Example: code in a separate window will format instantly while in a window with 100k lines with same code highlighted it will take a long while. This seems to indicate that it is considering all of the code even though it is only formatting a small piece.
2 votes -
move options settable under "SSMS > SQL Prompt > Options > Format > Style" page out of the Settings file and [back] into Style file
In version 7 the Style option FormatActionRemoveSquareBrackets was removed from the .sqlpromptstyle Style file into the .settings Settings file. I would like it moved back into the Style file, along with all other Style options settable under "SSMS > SQL Prompt > Options > Format > Style". See https://productsupport.red-gate.com/hc/en-us/requests/122489 for additional details.
2 votes -
16 votes
-
Conditionally place ON keyword on new line if exceeds specified wrap margin
My default preference is to maintain the ON keyword without a new line. I would like to be able to CONDITIONALLY place the ON keyword on a new line if, and only if the ON keyword together with the associated ON condition exceed a configurable wrap threshold.
Example:
-- Yield this >>>>
SELECT *
FROM Person.Address
INNER JOIN Person.StateProvince
ON StateProvince.StateProvinceID=Address.StateProvinceID
-- >>>> instead ofSELECT *
FROM Person.Address
INNER JOIN Person.StateProvince ON StateProvince.StateProvinceID=Address.StateProvinceID
-- Assuming the JOIN clause exceeds the wrap length
-- <<<This is particularly useful if the "Place JOIN table on new line" is NOT selected…
3 votes -
IN clause - indent according to parenthesis rules according to the expression they are in
It would be nice if the IN clause were formatted like a logical function that returns a value so that it followed the options and rules for parentheses and were indented according to its place in the logical expression. (paying attention to the ANDs and ORs if present)
2 votes -
Arithmetic expressions - format consistently with logical expressions
Arithmetical expressions and compound logical expressions all consist of operations and expressions with parentheses and orders of precedence. All of these should have the options for aligning operands, aligning parentheses, adding parentheses to make the default orders of precedence explicit. All expressions are subordinate to clauses so they should be indented under WHERE, ON, SELECT, WHEN.
1 vote -
Convert code to dynamic Code
Convert selected CODE or a complete stored procedure to Dynamic SQL Code.
16 votes -
Template based formatting with different
Template based formatting.
Select your text and right click, format according to template... then select the appropriate template of your choice.8 votes -
Auto generated INSERT needs a column blacklist
Add the ability to exclude columns from appearing in the auto-generated INSERT statements. I have to manually remove certain columns every time.
9 votes -
Align aliases, commas, datatypes and expressions at the next tab stop
I align aliases, commas, datatypes and expressions at the first tab stop following the longest element in the list. See examples below:
-- Tilde character used as space replacement to cope with HTML formatting
-- 2-character tabs are assumed below
-- In a fixed-space font, the commas, = signs, data types and AS keywords would all line up vertically
DECLARE
~~@x~~~~~~~~~~~~~~INT~~~~~~~~~,
~~@var~~~~~~~~~~~~VARCHAR(4)~~,
~~@longer_varname~VARCHAR(10)~,
~~@z~~~~~~~~~~~~~~DATETIME~~~~;SELECT
~~~~@longer_varname~=~'x'~~~~~~~,
~~~~@var~~~~~~~~~~~~=~'1234'~~~~,
~~~~@z~~~~~~~~~~~~~~=~GETDATE()~;SELECT
~~~~T1.shortfield~~~~~~~~AS~ShortField~,
~~~~AO.reallylongfield~~AS~LongField~~,
~~~~'x'~~~~~~~~~~~~~~~~~~~AS~XChar~~~~~~,
~~FROM~~~~~~~~dbo.table1~~~~~~AS~T1
~~~~LEFT~JOIN~dbo.anotherone~AS~AO~ON~T1.keyval~=~AO.keyval;EXEC~@x~=~dbo.SomeProc
~~@Param1~=~'3'~~~~~~~~~~~,
~~@P2~~~~~=~'Longer~Text'~,
~~@P3~~~~~=~4~~~~~~~~~~~~~;26 votes -
warn against data truncation
I would be nice if SQL-prompt could warn against posible data truncation.
Like assigning a int value to a tinyint field/variable or assigning a varchar(30) to a varchar(3).
I want it both at an global analysis (like find invalid objects) and in the current scrip edit (while modifying a trigger / procedure / function).13 votes -
prevent Prompt SQL from destroying bookmarks
If format SQL makes chnages - it destroy saved marks
This occurs even when line bookmarked line hasnt (visibly) changed
Very frushtrating3 votes -
Place space before END when collapsing shorter case statements
When collapsing CASE expressions shorter then XXX, the END has no space if there is a preceding parenthesis.
Example1 = CASE t1.Col004 WHEN 1 THEN t1.Col006 END,
Example1 = CASE t1.Col004 WHEN 1 THEN TRY_CONVERT(int, t1.Col006)END,0 votes
- Don't see your idea?