On 11 Mar 2019, at 20:21, Simon Slavin <[email protected]> wrote: > On 11 Mar 2019, at 7:30pm, Tim Streater <[email protected]> wrote: > >> What is the maximum size in bytes that a result set may be? And what happens >> if that size were to be exceeded? > > [The following is simplified for clarity. I discuss only worst cases and > ignore caching.] > > SQLite does not prepare an entire result set at once. Instead, it returns one > row each time you call sqlite3_step(). It's up to your own program to process > each row as it is returned. Since SQLite does not hold more than one row in > memory at once, theoretically there's no limit on how many rows it can return > for a single query.
[snip] > <https://sqlite.org/limits.html> Thanks for that, Simon. That would account for there being nothing on the limits.html page about a maximum result set size. My question came up because someone, using a language that has an API for a number of flavours of SQL (including SQLite), was experiencing a crash when his result set got to about a gig in size. So, as seems very often to be the case, it must be the interface API code to the SQLite library that was at fault. @Wout: nothing wrong with your reply, it was the TL:DR; version :-) -- Cheers -- Tim _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
