...which is required to call ffi::duckdb_interrupt:
extern "C" {
#[doc = "Interrupt running query\n\n connection: The connection to interrupt"]
pub fn duckdb_interrupt(connection: duckdb_connection);
}
There's no way to call duckdb_interrupt (and other ffi functions like it) with a Connection, as we can't access its fields. Exposing a Connection::interrupt() method would be one way around this.
I'm happy to make the contribution if the maintainers can advise on how you would like this implemented.
The
Connection
hides away the raw duckdb connection object in private fields:InnerConnection
contains affi::duckdb_connection
......which is required to call
ffi::duckdb_interrupt
:There's no way to call
duckdb_interrupt
(and otherffi
functions like it) with aConnection
, as we can't access its fields. Exposing aConnection::interrupt()
method would be one way around this.I'm happy to make the contribution if the maintainers can advise on how you would like this implemented.