fix(qe): Change Array(None) to return Null value. #5228
+5
−5
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.
Description
In PostgreSQL, a nullable array column can hold either a
null
value or an empty array ({}
), and these are semantically different. Previously, Prisma treated both cases as an empty array. This fix ensures that when the database returns anull
for a nullable array column, Prisma correctly returns anull
instead of an empty list.Related Issue
Changes Made
null
is properly recognized.Screenshots (if applicable)
Before the fix, the following query would return an empty array for a
null
column: