Skip to content

Conversation

@roji
Copy link
Member

@roji roji commented Jul 24, 2025

In the query shaper, we have two general paths around fixup:

  • For tracking queries, the change tracker is responsible for fixup
  • For non-tracking queries, we generate extra code into the shaper to do the fixup

This PR applies the non-tracking approach to complex types: since they aren't tracked separately like (owned) entities, we need to connect all complex types to their entity root.

Did some smoke testing as well with basic scenarios, everything seems to be working well.

Part of #36296

/cc @artl93

@roji roji requested a review from AndriySvyryd July 24, 2025 18:52
@roji roji marked this pull request as ready for review July 24, 2025 20:16
@roji roji requested a review from a team as a code owner July 24, 2025 20:16
@roji roji changed the title Support change tracking for complex JSON queries Support tracking queries for complex JSON queries Jul 24, 2025
@roji roji force-pushed the ComplexJsonChangeTracking branch from d32525b to 8894fe4 Compare July 24, 2025 22:10
@roji roji enabled auto-merge (squash) July 24, 2025 22:10
@roji roji merged commit 7181c41 into dotnet:main Jul 24, 2025
7 checks passed
@roji roji deleted the ComplexJsonChangeTracking branch July 24, 2025 23:21
@artl93
Copy link
Member

artl93 commented Jul 25, 2025 via email

@roji roji linked an issue Jul 29, 2025 that may be closed by this pull request
16 tasks
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.

Complex JSON query support

3 participants