Optimize eager loads map key generation - #1475
Merged
Merged
Conversation
This file contains hidden or 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
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.
Following up on #1473, I improved the map key generation logic.
Primitive values, strings and byte slices in particular, no longer go through
fmt.Sprintf, which reduces overhead. Numeric values are now handled by thestrconvpackage, which is faster and produces fewer allocations.SQL
driver.Valuertypes are unwrapped directly insidegenerateMapKey, which keeps the generated eager-loading code more readable and concise.generateMapKeyhandles the typical data types used as database keys efficiently, with a best-effortfmt.Sprintffallback for unrecognized types.Let me know, if anything is missing!