-
Notifications
You must be signed in to change notification settings - Fork 336
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
Implement cancellation of active reader #3
Comments
Is there any way the query can be canceled using the connection that's already open? |
My assumption is that the consumer would expect the active command to be cancelled (cooperatively by the database) and that the connection would remain usable afterwards. Thus, we cannot implement cancellation by passing the More specifically, the methods that expose cancellation are:
Handling the cancellation of a |
Implement reader cancellation. Fixes #3
Shipped in 0.17.0. |
The consumer should be able to cancel an active reader via
MySqlCommand.Cancel()
or theCancellationToken
passed toExecuteReaderAsync
etc.This probably needs to be implemented via
KILL QUERY
which may require a separate connection. It may be helpful to implement connection pooling #2 first and keep a spare connection around to issue this command.The text was updated successfully, but these errors were encountered: