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 memory demands can be reduced as much as needed by going back to the well a (potentially large) number of times.

Am I remembering this right? Can anyone refresh my memory on how to do it if so?

What are you seeing that leads you to believe that the results are too big to fit in memory?

Are you able to show us your query and how you are executing it from your language?





Best wishes,
@ndy

--
andy...@ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to