[5.0.1] Use default schema for view mappings #23278
Merged
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
ajcvickers
approved these changes
Nov 12, 2020
|
@AndriySvyryd Approved by Tactics for 5.0.1. |
AndriySvyryd
force-pushed
the
Issue23274
branch
from
3c2335c
to
641d553
Compare
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 #23274
Description
EF doesn't use the default schema for view mappings.
Customer Impact
The schema needs to be specified in all
ToViewcalls.How found
Reported by user on 5.0.0
Test coverage
This PR includes tests for the affected scenario.
Regression?
Yes, this used to work in 3.1
Risk
Low. The behavior is being reverted to what it was in 3.1