Skip to content

Conversation

@aarongable
Copy link

According to
https://github.blog/2020-05-20-three-bugs-in-the-go-mysql-driver/, when QueryContext is called with a context that is cancelled during scan, you can receive incomplete or corrupted results. As I understand it, the corruption is fixed upstream, but it's still possible to get incomplete results that will only show up in the error result from Close.

It's still possible and correct to call defer rows.Close(), since the database/sql docs say this:

https://godoc.org/database/sql#Rows.Close

Close is idempotent and does not affect the result of Err.

Note: This is a recreation of go-gorp#420

According to
https://github.blog/2020-05-20-three-bugs-in-the-go-mysql-driver/, when
QueryContext is called with a context that is cancelled during scan, you
can receive incomplete or corrupted results. As I understand it, the
corruption is fixed upstream, but it's still possible to get incomplete
results that will only show up in the error result from Close.

It's still possible and correct to call `defer rows.Close()`, since the
database/sql docs say this:

https://godoc.org/database/sql#Rows.Close

> Close is idempotent and does not affect the result of Err.

(cherry picked from commit 9179593)
@aarongable aarongable requested a review from a team as a code owner June 30, 2023 17:35
@aarongable aarongable requested a review from jsha June 30, 2023 17:35
@aarongable aarongable requested a review from pgporada July 5, 2023 18:36
@pgporada pgporada merged commit 792de22 into main Jul 5, 2023
@pgporada pgporada deleted the check-rows-close branch July 5, 2023 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants