168 results found
-
Autofix : SC002 – Script should end with empty line
SQL prompt currently removes the empty line at the bottom of a script, which then break rule SC002.
Can format include a setting to add a blank line at the bottom of a script, and also autofix sc002 issues.
3 votes -
Import and Export Aliases
It would be nice to have the ability to mass import/export aliases.
3 votes -
Ignore Begin statements with CTE immediately after
SQL Prompt's "Insert semicolon" function behaves weirdly when a CTE is a the start of a control loop. For example, if I have this code:
IF (1=1) BEGIN
WITH numbers AS (
SELECT 1 AS num
UNION SELECT 2
UNION SELECT 3
UNION SELECT 4
)
SELECT * FROM numbers
END;SQL Prompt will format it as
IF (1=1) BEGIN;
WITH numbers AS (
SELECT 1 AS num
UNION SELECT 2
UNION SELECT 3
UNION SELECT 4
)
SELECT * FROM numbers;
END;While the code runs, I think the semicolon after "BEGIN" makes very little sense. First, the beginning…
3 votes -
Add one additional Parenthesis style
My Teams would prefer this option:
xxxxxxxxxxxxxx (
xxxxxxx,
xxxxxxx )Opening parenthesis on the first line, and closing parenthesis on the last line.
Second and following lines indented one stop. This display seems to strip out the leading spaces.
3 votes -
Make parentheses rules customizable (where what applies) instead of a global setting
I have different wants for parentheses rules: Collapse short content or not, Having Parentheses on separat lines or leading the content, etc. It all depends on the context. But currently the setting is global.
I would like to be able to define one rule for, say, Primary Key definitions, and another rule for, say, the columns of a table.
I would want one thing for Control Flow sections, and another thing for Variables declarations.Today, I need to choose which one to be dominant (or stop using FORMAT SQL on the entire script, but just highlight the block where I…
3 votes -
Closing parenthesis and content indention on APPLY/EXISTS not indenting
It seems that the contents and closing parenthesis of EXISTS and APPLY clauses is not being indented as I would expect. So either i'm weird....or Format SQL is doing it wrong?
I'm using (
.....this parentheses style
)What it's doing:
SELECT *
FROM tblA a
WHERE 1 = 1
.....AND EXISTS (
.....SELECT *
.....FROM tblB b
.....WHERE b.Col1 = a.Col1
..........AND b.Col2 = a.Col2
..........AND b.Col3 = a.Col3
)What I expect:
SELECT *
FROM tblA a
WHERE 1 = 1
.....AND EXISTS (
..........SELECT *
..........FROM tblB b
..........WHERE b.Col1 = a.Col1
...............AND b.Col2 = a.Col2
...............AND…3 votes -
Align BETWEEN with comparison operators
It's currently possible to align operations in WHERE which is great, but BETWEEN is not aligned.
Example - currently:
WHEREModifiedDate BETWEEN DATEADD(MONTH, -6, GETDATE()) AND GETDATE()
AND City__________= 'Bothell'
OR LEFT(PostalCode, 2)= 'CB'
OR PostalCode_______= @prefix + @suffixExpected:
Example - currently:
WHEREModifiedDate_BETWEEN DATEADD(MONTH, -6, GETDATE()) AND GETDATE()
AND City________= 'Bothell'
OR LEFT(PostalCode, 2)= 'CB'
OR PostalCode_______= @prefix + @suffix3 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 -
End column guide lines
I think SSMSBoost has this feature: being able to add configurable guide lines to limit the query writing space to a specified number of characters/columns. This is very handy as I always want to keep my code narrow, within the 80-char limit. Currently, I have to install SSMSBoost for it... Could this please be added to SQL Prompt? This is probably a quick feature to implement and would be tremendously useful. Thanks.
3 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 -
2 votes
-
DDL comma placement
When making a CREATE TABLE statement, I would like to have the comma at the beginning of the line.
I've set the lists.placeCommasBeforeItems property to true, but it's not working for the DDL statement.So either fix the comma placement option for DDL statements or add an option for it.
2 votes -
Include some menu options directly in Style format
Would it be possible to include the attached menu options in the Style format configuration? It would be very helpful to have it when Formatting SQL instaead of executing it after the Format.
At least, "Apply Casing Options", "Qualify Object Names" and "Remove Square Brackets".2 votes -
Maintain TABs before comments
We have some comments placed in the code preceeded by one or more TABs. When formatting SQL all these TABs are replaced by one WHITESPACE.
Is it possible to maiantain these TABs?See attached examples.
2 votes -
Semicolons deletion
We would like an option to get rid of the semicolons. You can only configure the whitespace. When we apply "Format SQL" many semicolons are inserted in our code and we don't wnat them.
Is it possible to add an option when formatting Style for eliminating semicolons?2 votes -
Format Join Order
On our team we are very particular about the order of our joins as they are written in the query. I would like to request an option to format joins so the table you are joining on is the first item in the join. In the example below you join to tableb so the first ON clause is tableb, subsequently on the tablec join the first join is on objects from tablec.
SELECT (columns)
FROM tablea a
INNER JOIN tableb b ON
a.id = b.id
INNER JOIN tablec c ON
b.id2 = c.idTo:
SELECT (columns)
FROM tablea a
INNER…2 votes -
Have formatting features for cross join match those of left/right/inner join
I have set up rules to format as such:
Select *
From Employees e Join
People p On e.PersonID = p.PersonID;Each table/view object aligned on a new line. However, when I convert to a "cross join", they don't generate a new line, they concatenate on the same line, like such:
Select *
From Employees e Cross Join People p;2 votes -
Additional options for formatting a GROUP BY clause
It would be appreciated if you could enhance the SqlPrompt Formatting Styles functionality. I believe this would go in the STATEMENTS >>> Data (DML) section.
I'd like to continue using the "If there are multiple expressions" item of the "Place GROUP BY / ORDER BY expression on new line" drop-down. But I'd like those expressions to be indented; they presently all left-align to the GROUP BY.
Also, while you're there, it seems that it would be good to also have add an "If longer than wrap column" option to the above-mentioned drop-down.
2 votes -
Refactoring an INSERT statement into an UPDATE statement with SELECT
Be able to refactor INSERT statement into UPDATE statement that has SELECT rather than VALUES i.e. "insert into xxx select from".
2 votes -
DDL Parentheses Formatting should apply to VALUES clause of INSERT Statements - Bug?
The current parenthesis options I have set for an INSERT INTO (DML) statement, only appear to work for the list of columns, but NOT for the list of values in the VALUE clause. I'm unsure why this behaviour is different, but this inconsistency seems like a bug.
I have provided a screenshot where you can clearly see the parentheses are not aligned correct in comparison with the INSERT statement.
Ultimately I would like for the formatting to be overall consistent.
2 votes
- Don't see your idea?