opt: fix error in case of casted NULL arguments to AddGeometryColumn #51226
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.
This commit fixes an error that occurred when
AddGeometryColumn
wascalled with
NULL
arguments that were cast to the type specified by thefunction signature. #50992 already fixed the case when
AddGeometryColumn
was called with bare
NULL
arguments, since those were detected byTypeCheck
.TypeCheck
does not detectNULL
arguments if they are cast to the correcttype.
This commit fixes the error by adding an explicit check in the
optbuilder
that each argument is not null before calling the
SQLFn
of theAddGeometryColumn
overload.Informs #50296
Release note (bug fix): Fixed an internal error that occurred when
AddGeometryColumn was called with NULL arguments. This now results in
a no-op and returns NULL.