Interrupt causes any pending database operation to abort and return at the earliest opportunity.
|Arguments:||There are no arguments to this method.|
|Remarks:||This method is safe to call from a different thread than the thread that is currently running the database operation. But it is not safe to call this routine with a database connection that might close beforeinterruptreturns. If a SQL operation is very nearly finished at the time wheninterruptis invoked, then it might not have an opportunity to be interrupted and might continue to completion. A SQL operation that is interrupted will return INTERRUPT result code. If the interrupted SQL operation is an INSERT, UPDATE, or DELETE that is inside an explicit transaction, then the entire transaction will be rolled back automatically. Theinterruptcall is in effect until all currently running SQL statements on this database connection complete. Any new SQL statements that are started after theinterruptcall and before the running statement count reaches zero are interrupted as if they had been running prior to theinterruptcall. New SQL statements that are started after the running statement count reaches zero are not effected by theinterrupt. A call tointerruptthat occurs when there are no running SQL statements is a no-op and has no effect on SQL statements that are started after theinterruptcall returns. If this database connection closes whileinterruptis running then bad things will likely happen.|
|Details:||The functionality of theinterruptmethod is similar to that of the SQLite sqlite3_interrupt API.|