[release/8.0] Add complex type mappings to the default relational mappings #32901
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
AndriySvyryd
changed the title
AndriySvyryd
approved these changes
Jan 23, 2024
|
Note that the branch is currently closed. |
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.
Port of #32867
Fixes #32699
Description
Raw SQL queries with
FromSqluse different default type mappings than other queries. These mappings were not correctly updated for complex types, a new feature in 8.0.Customer impact
FromSqlqueries for entity types that contain complex types will throw.How found
Customer reported on 8.
Regression
No, complex types is a new feature in 8.
Testing
Tests added.
Risk
Low. Quirked.