OptionalerrorOptional ReadonlyinflightControls what happens when the signal is aborted while a query is in-flight.
'ignore query' stops waiting for query results. The query continues running
on the database server, and the connection is released back to the pool only
after the in-flight query settles.
'cancel query' attempts to cancel the query on the database side (e.g. pg_cancel_backend
in PostgreSQL or kill query in MySQL). This requires the dialect's connection
to implement DatabaseConnection.cancelQuery. Otherwise, falls back
to 'ignore query' with a warning. Writes (insert, update, delete) are not
cancellable in most database engines, so your mileage
may vary. Also, some databases do not cancel the running query immediately
resulting in changes being committed sometimes - consider 'kill session'
when you need stronger guarantees, at all costs.
'kill session' attempts to kill the database process/session the query is
running in (e.g. pg_terminate_backend in PostgreSQL) and with it any running
queries, transactions and obtained locks. This requires the dialect's connection
to implement DatabaseConnection.killSession. Otherwise, falls back
to 'cancel query' with a warning. Killing the session is very aggressive,
and will require reconnection on the next database operation if there are
no idle connections available in the pool.
Default is 'ignore query'.
Optional ReadonlysignalAn optional signal that can be used to abort the execution of (async) operations.
This is useful for cancelling long-running queries, for example when the user navigates away from the page or closes the browser tab.
See inflightQueryAbortStrategy for handling of database side query.
An optional error constructor that is used to create an error when the query returns no results.
By default, an instance of NoResultError is thrown.