Fix comparison of numeric jsonb columns #22
Merged
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.
Since we use
->>
onjsonb
fields we always get a string back. Comparisons such as<
and>
were done on string values which gives unexpected results.I have tried various other approaches that failed.
jsonb
doesn't work because you can't cast query params tojsonb
.CASE WHEN
withjsonb_typeof
doesn't work because eachWHEN
of aCASE WHEN
needs to return the same type.Convert
recursively for$elemMatch
where you then don't know the column type anymore.