On 9/8/06, A. Klitzing <[EMAIL PROTECTED]> wrote:
Jay Sprenkle schrieb:
> On 9/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>> The only way I know to provide some approximation of random
>> access cursors for queries like the above is to store the
>> complete result of the query in a temporary table. You can
>> always do so by prepending:
>
> Did anyone suggest doing that to them? It seems a simple matter
> to select the unique keys from the set you want and cache them.
What do you mean? That's the same problem like above. ;-)
SQL is not really designed for direct record level access.
It really works well for operating on sets.
You can have a set of one row, so it can be done.
There is no problem to have the resultset in a temp table.
I think we will use a cache for a cache now to avoid massive
SELECT-usage... that isn't pretty but it will work.
That is what I was thinking too. You build a list of unique identifiers
in a temp table or cache of the rows you want to access. Then use
select to access single rows using the identifiers.
--
SqliteImporter and SqliteReplicator: Command line utilities for Sqlite
http://www.reddawn.net/~jsprenkl/Sqlite
Cthulhu Bucks!
http://www.cthulhubucks.com
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
