Small Change: Allow calling struct.Exists() without having to pass on PK fields #1202
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.
For when having a helper interface that has Insert(), Update() and Upsert().
Upsert() is not always possible, e.g. if table has only one field (the PK); or composite PK (mysql).
An alternative is necessary. Therefore, knowing whether the record exists helps to decide between Insert() and Update().
This enables e.g. generic mass loads from external files.
Workaround for #328, if you e.g. flag upsert-incompatible tables and use interface such as above.
Example
troublesome table in question
result of template execution