-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error happened but not returned to the client #48446
Labels
type/enhancement
The issue or PR belongs to an enhancement.
Comments
13 tasks
This was referenced Nov 9, 2023
13 tasks
This was referenced Dec 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enhancement
By reproduce #48411 and after reading the code, I found it might not be the only case that
error happened but not returned to the client.
terror.Call
ignores error, so the error is not returned to the client.But NOTE, even we to write it as this, the code is still wrong:
The problem is that after we
writeEOF()
, we finish this mysql response telling the client that all the data is done.So even we find an error later (for example, in defer rs.Close()), there is no way to tell the mysql client any more!
The correct order should be:
The text was updated successfully, but these errors were encountered: