fix: use correct receivers for custom database types #456
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
We must use mixed pointer and non-pointer receivers for our custom database types to satisfy both the sql.Scanner and driver.Valuer interfaces. Tests have been added to ensure that our custom types are working as they are supposed to. Signed-off-by: Aurora Gaffney <[email protected]>
wolf31o2
approved these changes
Mar 9, 2025
verbotenj
approved these changes
Mar 9, 2025
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.
We must use mixed pointer and non-pointer receivers for our custom database types to satisfy both the sql.Scanner and driver.Valuer interfaces. Tests have been added to ensure that our custom types are working as they are supposed to.