Fix RowBinary tuple encoding re-normalizing nested types - #378
Merged
ruslandoga merged 1 commit intoAug 9, 2026
Merged
Conversation
Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
Collaborator
|
Thank you! |
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.
Fixes #367.
encode({:tuple, types}, values)called the publicencode_row/2, which runsencoding_types/1again. The tuple's field types were already normalized byencoding_type({:tuple, ts}), so encoding a tuple with a normalized nested type likeDateTime64orTime64re-appliedtime_unit/1to an already-computed value (e.g.1000) and raisedFunctionClauseError.Switched the tuple clause to the private
_encode_row/2, which assumes normalized types and skips the second pass. Added a round-trip regression test forTuple(DateTime64(3, 'UTC'))andTuple(Time64(6)).