Add null safety to PostGISCodec #2260
Merged
Conversation
This file contains 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
If a column contained a null geometry the registered Geometry ColumnMapper would throw a NPE while trying to convert the null value to a byte array. If a null value is now processed by the ColumnMapper a null value is returned
|
Kudos, SonarCloud Quality Gate passed!
|
spannm
approved these changes
Jan 26, 2023
stevenschlansker
approved these changes
Jan 26, 2023
stevenschlansker
added a commit
that referenced
this pull request
Jan 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If a column contained a null geometry the registered Geometry ColumnMapper (from PostGISCodec) would throw a NPE while trying to convert the null value to a byte array.
If a null value is now processed by the ColumnMapper, a null value is returned