On 5/4/17, Chris Locke <[email protected]> wrote: > If sqlite is given a slightly misconfigured SQL statement (eg, incorrect > JOIN statements), it could potentially try and retrieve millions of rows. > (Question taken from here: > https://github.com/sqlitebrowser/sqlitebrowser/issues/1005) > > Is there any way of hooking into this before the actual records are > retrieved, or a way of (cleanly) terminating a query after a period of time?
Can you get the application to use the sqlite3_interrupt() (https://www.sqlite.org/c3ref/interrupt.html) interface to stop the long-running query? -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
