Skip to content

Fix indexing on nested complex JSON collections #37017

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix indexing on nested complex JSON collections #37017

wants to merge 1 commit into from
+144 −20

Conversation

@roji
Copy link
Member

@roji roji commented Oct 23, 2025 •
edited
Loading

This fixes two distinct bugs:

  • Our current (hacky) mechanism for pre-visiting and rewriting collection indexing and projection (see #36335) did not support accessing non-collection complex properties before the actual collection property (e.g. the Foo in Where(b => b.Foo.Bar[0].X == 8).
  • The SQL Server ElementAt translation ignored the path on the incoming OPENJSON when transforming it to JSON_VALUE.

Fixes #37016

@roji roji requested a review from a team October 23, 2025 10:18
@roji roji enabled auto-merge (squash) October 23, 2025 10:19
@roji roji force-pushed the Nestedcollection branch from 20a999b to 4b15cbf Compare October 23, 2025 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Indexing over nested complex JSON collections fail

1 participant

@roji