Andrew Shakinovsky wrote:
I have noticed with SQLite (at least this was true with 2.8x, not sure about
3x) that if you try to use an ORDER BY with a table that doesn't have an
index on the field you are ORDERing by, it will do the entire sort
(presumably just the keys) in memory. This will cause you to run out of
memory if the table is too large.
This is also true of version 3.0 and (the soon to be released) version
3.1. I believe this constraint is documented somewhere, though I
cannot say where right off hand. Somebody please correct me (and
submit documentation patches) if I am wrong.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
