Paul Sanderson wrote: > I have users who need to execute queries that generate a large number > of rows, I have other users that create queries that generate a large > number of rows by accident (i.e. cross joins). I have no control over > what they enter but I want to do something to warn them that their > query might result in an over large number of rows and a limit clause > might be a solution.
This does not protect against a query that computes many things but does not actually return many rows. Just allow them to cancel the query; use sqlite3_progress_handler(). Regards, Clemens
