Move to using sqlite3_errmsg to extract a contextual error for SQLite failures #2352
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.
Change
Use
sqlite3_errmsg
to get an error message with actual context as opposed to the string for the error code. We can always look up the error code string if needed, and we will get the string for the HRESULT version in the logs as well.For instance, the message for the new test is now:
Rather than the prior "Bad SQL" type default value.
Validation
All unit tests pass, manually confirmed more useful error messages in at least some cases.
Microsoft Reviewers: Open in CodeFlow