> Le 4 mai 2017 à 17:49, Chris Locke <[email protected]> a écrit : > > 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?
http://sqlite.org/c3ref/interrupt.html <http://sqlite.org/c3ref/interrupt.html> -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia, http://integral.software _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
