-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stored procedure handling #60
Stored procedure handling #60
Conversation
Added the parameter's direction and the null ability.
…g information on-top instead formatting the sql-command itself.
The SqlServerFormatter now handles the stored procedures in a special way like respecting the parameter directions (output, return). All sql statements threaten by the SqlServerFormatter are now terminated via a semicolon.
This covers standard sql queries as well as the new stored procedure handling.
Thank you for pointing the new commit out, I'm gonna fix it right now. Regarding the examples: DELCARE @x int = 123,
@y int = 456;
dbo.SomeProcedure; With my modification however everything is well handled: DELCARE @x int = 123,
@y int = 456;
EXEC dbo.SomeProcedure @x = @x, @y = @y; I even care about output params as well as return params: DELCARE @x int = 123,
@y int = 456,
@outGoesHere int = null,
@retVal int;
EXEC @retVal = dbo.SomeProcedure @x = @x, @y = @y, @outGoesHere = @outGoesHere OUTPUT;
SELECT @retVal as ReturnValue; I could write the stored procedure call like this |
(introduced by 02a7de9)
any updates @yellis? would be cool if it would be included in the next release. |
Hope to get to it soon, but as it has regression potential need to test a On Tue, May 13, 2014 at 5:57 PM, Bernhard Millauer <notifications@github.com
|
Hi @yellis, sorry to bother you. |
Hi guys, any updates on the PR? |
Wonderful, thank you. Is there an ETA for the release? |
ETA on release 3.0.11 is about 2 hours ago. Please let me know if there are any issues. |
looks good! I might change a small bit but this will be done in another PR. the functionality is there and works as expected. thanks @yellis |
good to hear |
…ed procedure formatting enhancements from #60. Nuget to v3.1.
Please use release v3.1+ if you want to take advantage of the features included here (they were included in v3.0.11 but removed from v3.0.12, for reasons discussed in #68). |
Here I added the handling of stored procedure calls.
I put a lot of detail on the copy/paste-ability of the existing handling as well on the new one.
I also changed the VerboseSqlServerFormatter to only add information on top of the existing output instead building the same output.
This PR is connected with #48