WIP - Null fields are ignored when scanning to a model struct #7233
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.
What did this pull request do?
We're having issues reading a row into a struct with nullable fields, represented by the
guregu/null.v3
types; specifically in the case where the columns in the table have been updated from non-null to null. e.g.In this case we'd expect the struct field to be set to
null.Time{}
but what we find is that the field is left unchanged. I've tracked the issue down to this commit and I can't make out what the intention of the change by looking at the previous logic:The commit in question mentions fixing a problem related to time fields but this block looks unrelated.