Repository navigation
[9.0] Preserve row value type mappings when rewriting expressions - #3955
Merged
Merged
Conversation
The global tuple mapping could be enabled after the query-filter test pool was already created, causing test-order-dependent tuple reads to fail. Configure it on the regression data source instead. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 79a22b3a-d5f9-4921-ac7b-3a1b41a9adc1
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
9.0 backport of #3953 (8912932).
Preserves
TypeMappingwhenPgRowValueExpression.VisitChildrenorUpdaterewrites children, fixing tuple projections over query-filtered navigations. Includes the seeded sync/async regression and rewrite/no-op identity unit coverage.Only release-branch adaptations: EF 9's
InitializeAsync/CreateContexttest APIs, nullable-disabled test conventions, and query-filter parameter naming. No SDK or dependency configuration changes.Validation on .NET SDK 9.0.312 and PostgreSQL 18.4:
PgRowValueExpressionTestcases passed.Fixes #3933.