On 1/31/17, Jens Alfke <[email protected]> wrote: > > My immediate workaround (implemented last night) is to iterate over the > statement at the moment the query is run, saving all the rows in memory. Our > enumerator object then just reads and returns successive rows from that > list.
That's how client/server SQL database engines do it. They run the query to completion before starting on any of the updates. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
