Add HexVal and HexNum type support to evalengine.Expr #9616
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 this commit 0d1a5e5, which was part of #9351, we broke
HexVal
andHexNum
type support withVindexes
.More specifically,
HexVal
andHexNum
type support in vindex functions was lost in the transition fromsqltypes.PlanValue
toevalengine.Expr
.This work aims to add support for the
HexVal
andHexNum
types inevalengine.Expr
.Related Issue(s)
Checklist