Activity overview
Latest activity by DaveB
Yes, I am aware of those settings and yes they make a difference, but I don't care for how it then indents the procedure parameters and parenthesis.
I think that table variables and function / procedure definitions need to be handled via separate formatting settings.
Thanks for the response.
-Dave / comments
Yes, I am aware of those settings and yes they make a difference, but I don't care for how it then indents the procedure parameters and parenthesis.
I think that table variables and function / proc...
How about $PASTE$ to paste current clipboard into snippet
It would be useful to write a snippet that you could paste the contents of the clipboard into it. The contents might contain the name of an object (table, view) that needs to be entered based on t...
Table Variables formatted with schema settings
When I enable the Schema statements settings:
New Line on Open parenthesis of a definition
New Line on First definition
New Line on Closing parenthesis of a definition
and then format a stored pro...
I'm trying to report a bug. The bug is that the setting DoNotIndentProcedureContents does not work correctly when IndentBeginToken equal False. The bug is reproduced by editing the config file because there is no way to change the IndentBeginToken setting through the UI. The edits I made are: CASE 1: IndentBeginToken = False
DoNotIndentProcedureContents = True
PROBLEM:
This causes the contents of a stored procedure to be indented. It should not. CASE 2: IndentBeginToken = False
DoNotIndentProcedureContents = False
PROBLEM:
This causes the contents of a stored procedure to not be indented. It should be indented.
If you set IndentBeginToken to True, then DoNotIndentProcedureContents works as expected.
-Dave / comments
I'm trying to report a bug. The bug is that the setting DoNotIndentProcedureContents does not work correctly when IndentBeginToken equal False. The bug is reproduced by editing the config file be...
Another vote for the comment alignment feature!
-Dave / comments
Another vote for the comment alignment feature!
-Dave
Sorry for not being clear. The result is exactly what I want but the settings to achieve the result are not what I expected. The issue appears to be that there is a conflict between the IndentBeginToken setting and the DoNotIndentProcedureContents setting in RedGate_SqlPrompt_Format_Layout_LayoutOptions.xml.
If I set IndentBeginToken = False and DoNotIndentProcedureContents = True, my stored procedure contents are indented.
If I set IndentBeginToken = False and DoNotIndentProcedureContents = False, my stored procedure contents are NOT indented.
This means that the DoNotIndentProcedureContents logic is backwards when IndentBeginToken = False.
-Dave / comments
Sorry for not being clear. The result is exactly what I want but the settings to achieve the result are not what I expected. The issue appears to be that there is a conflict between the IndentBeg...
I just turned the "Indent contents" under "Schema statements" on while leaving the option "IndentBeginToken" set to False and now the initial begin statement of my stored procedure does NOT indent which is what I was trying to achieve! So now it works exactly how I want but this seems like a small issue.
To recap:
1. Set IndentBeginToken to False in the RedGate_SqlPrompt_Format_Layout_LayoutOptions.xml file.
2. Uncheck "Indent contents" under "Schema statement"
3. Run formatting and contents Do indent
4. Check "Indent contents" and rerun formatting and contents do Not indent
-Dave / comments
I just turned the "Indent contents" under "Schema statements" on while leaving the option "IndentBeginToken" set to False and now the initial begin statement of my stored procedure does NOT indent ...
Trying the IndentBeginToken format option and found an issue
I typically don't indent begin statements and so I started hunting through your xml and found the file FormattingOptions.xml and the formatting option IndentBeginToken. This does just what I want;...