chore: add CompileJsonValues to normalize values for JSON queries#50
Merged
chore: add CompileJsonValues to normalize values for JSON queries#50
Conversation
hwbrzzl
reviewed
Jun 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 JSON queries, certain database drivers (e.g., PostgreSQL) require numeric and boolean values to be passed as strings when used in JSON comparisons. Passing raw integers, floats, or booleans directly can result in encoding or type mismatch errors such as
unable to encode into text format for text (OID 25). This change introduces a normalization step to convert numeric and boolean values (including their pointer and slice variants) into string format for consistent behavior across different drivers.✅ Checks