189 results found
-
Trimming trailing spaces in comments
It would be cool if SQL Prompt was able to remove trailing whitespaces/tabs not only for T-SQL, but also for comments.
It's not something crucial, but rather nice-to-have
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 -
Option to display values within IN statements without spaces between them
Another white space removal feature to suggest.
The ability to format all IN statements as:
empType IN ('a','b','c','d')Rather than the default:
empType IN ('a', 'b', 'c', 'd')I have done some exploring in the formatting styles and scouring the forums here and this feature doesn't seem to be available.
2 votes -
SQL Prompt - More Granular Suggestion. WHERE AND / CASE AND
SQL Prompt - More Granular Suggestion. WHERE AND / CASE AND
Would you add a couple of settings that give users more granular control in formatting SQL Prompt, please?
In the CASE section, please add a section on how to handle Case AND statements, if we want the AND on a new line or the same line, and where to Align the AND.
Also, please add a checkbox to align any '=' signs, like CASE WHEN colA = 1 then 1 else. I'd like all = signs to line up when there are multiple WHEN statements.
Also, Please add a…
2 votes -
Option to Change != to <>
Although used quite often, != is not ANSI compliant for NOT EQUAL. Have an option in SQL PROMPT Code Formatting to automatically replace != with the ANSI compliant <>.
2 votes -
Aliases for synonyms
When using a synonym, the alias name generated is based on the synonym orginal table, not in the synonym name.
So, if I have a synonym named sch1.ShortTableName that maps on AnotherDatabase.sch2.TableWithLongAndComplexName
If I write
SELECT * FROM sch1.ShortTableName
It ends being
SELECT * FROM sch1.ShortTableName AS twlacn
It would be good that in case of synonyms, the alias name was based on the synonym name, not on the source object name.
Or to keep backwards compatibilty, to have a setting that lets us choos either to follow the synonym name or the source object name.
2 votes -
Allign all euals of a set part in an updatestatement
Allign all equals of a set part in an update statement
2 votes -
2 votes
-
Can we add option to have "WITH (NOLOCK)" in the Aliases tab in the Options
Can we add option to have "WITH (NOLOCK)" in the Aliases tab in the Options
2 votes -
CREATE TABLE align data-types
When making a CREATE TABLE statement, there should be a formatting option to align the data-type behind the field names.
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 -
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 -
Stop OPENJSON after CROSS APPLY from showing up on new line
I have included a Sample SQL script. This script shows the desired formatting. I can't find any way to prevent the OPENJSON from being sent to a new line. For example:
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY OPENJSON(OJ.Value)
WITH (ID int) AS CAOJbecomes
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY
OPENJSON(OJ.Value)
WITH ( ID INT ) AS CAOJ2 votes
- Don't see your idea?