Fix Issue 1329 - agtype_to_int4 crash (#1339) #1344
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.
Fixed issue 1329 where
agtype_to_int
<8,4,2> andagtype_to_int4_array
crashed due to not properly checking input.As these functions take "any" input, the input has to be properly checked before casting it to a specific type. The input section assumed it was agtype, which caused crashes for non-agtypes.
The functions
agtype_to_int
<8,4,2> will convert non-agtypes into agtype. However, there were no regression tests for this.The functions
agtype_to_int
<8,4,2> will convert non-agtypes to agtype ints but, did not for their string equivs. Meaning, passing a ('true') or ('3.14') would fail but, passing a (true) or (3.14) would not. This has been corrected for all 3 functions.TODO -
The function
agtype_to_int4_array
only takes agtype, currently, and we should consider allowing it to take "any" types.Added regression tests.
Added missing regression tests.