lint: rowserrcheck #1164
Merged
lint: rowserrcheck #1164
Conversation
This file contains 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
It turns out `rows.Next()` can return false on error, avoiding error detection with `rows.Scan` See golangci/golangci-lint#945 Fix that. In particular, `QueryRowContext` with checking for `sql.ErrNowRows` is much simpler when expecting 0 or 1 results Mark two false positives when only wanting schema of `LIMIT 0` query
iskakaushik
approved these changes
Jan 26, 2024
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.
It turns out
rows.Next()can return false on error, avoiding error detection withrows.ScanSee golangci/golangci-lint#945
Fix that. In particular,
QueryRowContextwith checking forsql.ErrNowRowsis much simpler when expecting 0 or 1 resultsMark two false positives when only wanting schema of
LIMIT 0query