fix(drizzle): support equals polymorphic querying with object notation #8316
+121
−12
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.
Previously, this wasn't valid in Postgres / SQLite:
Now it works and actually in more performant way than this:
Why? Because with the object notation, the output SQL is:
movies_id = 1
- checks exactly 1 column in the*_rels
table, while with the separate query byrelationTo
andvalue
we need to check against each possible relationship collection with OR.