Bump SQL Tools version to 4.9.0.3 (#23813) #23828
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
corivera
requested review from
Charles-Gagnon,
alanrenmsft and
kburtram
as code owners
|
@corivera You should be using a build from the release/4.8 branch of STS, not from main. Please port your change over to that branch and generate a build from there (which will have a 4.8 version number) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #23729
A recent change for the database properties dialog was causing the RestrictAccess setting to be set to null, which resets the value to SINGLE_USER. We should be doing MULTI_USER by default, so the fix in STS was a simple null check.