add DriverErr to retrieve the original database error #11
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.
Hi Russ,
I really like that package, I feel it's just the right (thin) set of features above Go's database package. The only thing I felt was missing was a way to retrieve the original driver's error, as it was hidden away by the
fmt.Errorf
calls. It can be important to determine what caused the error (e.g. duplicate row, constraint error, etc.). So I added an internal error type that wraps the original error and preserves the same error messages as before, but with aDriverErr
function to be able to retrieve that original error.There's also a test for that new feature.
Thanks,
Martin