We're already executing queries and fetching results in a separate thread, so this might be as easy as sending the right signal to the adapter's connection from the main thread (or probably better another worker thread), and then handling the exception that is raised.

adapter implementation details:

duckdb: call interrupt() on the DuckDBPyConnection.
sqlite: call interupt() on the sqlite3.Connection.
pg: call cancel() on the psycopg2.Connection (raises QueryCanceledError)
mysql: will need to get the right connection_id, and then create a new cursor and execute a kill query <cnx-id> query: https://stackoverflow.com/a/70251287/10813082
odbc: not generally supported; for sqlserver, like mysql, but need to kill the whole connection with kill <process_id> docs

Add an optional adapter interface for canceling queries #333

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions