Skip to content
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

Connect-DbaInstance - Optimize code for StatementTimeout and ApplicationIntent #7524

Merged
merged 8 commits into from
Jul 12, 2021

Conversation

andreasjordan
Copy link
Contributor

As StatementTimeout is an integer variable with a default from an integer configuration - this can never be $null. So we always set this.
But to not copy connection context if not needed, added a test like for Database and NonPooledConnection. Then did that also with ApplicationIntent to have them all aligned.

andreasjordan and others added 5 commits July 11, 2021 20:23
Co-authored-by: Shawn Melton <11204251+wsmelton@users.noreply.github.com>
Co-authored-by: Shawn Melton <11204251+wsmelton@users.noreply.github.com>
Co-authored-by: Shawn Melton <11204251+wsmelton@users.noreply.github.com>
@potatoqualitee
Copy link
Member

All tests pass and Shawn's changes have been addressed 👍🏼 Merging

@potatoqualitee potatoqualitee merged commit 1db2fb0 into development Jul 12, 2021
@potatoqualitee potatoqualitee deleted the ConnectDbaInstance_StatementTimeout branch July 12, 2021 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants