Skip to content

fix: prevent nullifying nested objects with non-null values in left joins#5986

Open
namdamdoi68-oss wants to merge 2 commits into
drizzle-team:mainfrom
namdamdoi68-oss:agent/namdamdoi68-oss/issue-1603
Open

fix: prevent nullifying nested objects with non-null values in left joins#5986
namdamdoi68-oss wants to merge 2 commits into
drizzle-team:mainfrom
namdamdoi68-oss:agent/namdamdoi68-oss/issue-1603

Conversation

@namdamdoi68-oss

Copy link
Copy Markdown

Fixes #1603

Description

This PR fixes a bug where a nested select object under a left join is incorrectly nullified when its first property is null, even if subsequent properties have non-null values.

We update the logic to set the nested object's entry in nullifyMap to false if any non-null column value is encountered for that object.

@algora-pbc /claim #1603

@namdamdoi68-oss namdamdoi68-oss force-pushed the agent/namdamdoi68-oss/issue-1603 branch from 9e30ddf to 082935a Compare July 12, 2026 00:19
@namdamdoi68-oss

Copy link
Copy Markdown
Author

Hi, I have rebased this PR on top of the latest main branch to resolve the behind state. The changes are up to date and clean. Please let me know if you need any adjustments or if this is ready to be reviewed. Thank you!

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.

[BUG]: Nested Partial Select returns null on left join if first column value is null

1 participant