Re: [sqlite] Getting "chunked" output from a large SELECT operation.

2019-10-16 Thread Andy Bennett
Hi, I'm having a situation where the results of a large SELECT operation are apparently too big to fit in memory. Obviously I could jerry-rig something to work around this, but I have a vague recollection that SQLite provides a nice way to get the results of a query in "chunks" so that the

Re: [sqlite] Getting "chunked" output from a large SELECT operation.

2019-10-16 Thread Kees Nuyt
On Wed, 16 Oct 2019 17:38:28 +, you wrote: > I'm having a situation where the results of a large > SELECT operation are apparently too big to fit in memory. > > Obviously I could jerry-rig something to work around > this, but I have a vague recollection that SQLite > provides a nice way to

Re: [sqlite] Getting "chunked" output from a large SELECT operation.

2019-10-16 Thread David Raymond
ct: [sqlite] Getting "chunked" output from a large SELECT operation. I'm having a situation where the results of a large SELECT operation are apparently too big to fit in memory. Obviously I could jerry-rig something to work around this, but I have a vague recollection that SQLite provides

Re: [sqlite] Getting "chunked" output from a large SELECT operation.

2019-10-16 Thread Simon Slavin
On 16 Oct 2019, at 6:38pm, Randall Smith wrote: > I'm having a situation where the results of a large SELECT operation are > apparently too big to fit in memory. SQLite only stores results if it has to. It would have to if there is no good index for your SELECT terms. Are you actually using

[sqlite] Getting "chunked" output from a large SELECT operation.

2019-10-16 Thread Randall Smith
I'm having a situation where the results of a large SELECT operation are apparently too big to fit in memory. Obviously I could jerry-rig something to work around this, but I have a vague recollection that SQLite provides a nice way to get the results of a query in "chunks" so that the memory