Add error handling for nil builders when calling Exec for Upsert #4056
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.
A small contribution to add a check to the Exec call as part of the Upsert functionality.
Occasionally I would see cases where developers mistakenly construct a slice of builders usually by instantiating a slice with a set length and then not setting a builder for each index resulting in nils being passed to the CreateBulk method.
This would then result in a panic from the Exec call when it tries to call len on the b.conflict property.
This change checks if b is nil and returns an error to hopefully help people more easily debug this type of issue.