> > I cache the items I'm displaying in an STL vector (C++). If the user moves
> > to a page where I have no data I load it from the database as needed. I was
> > considering loading data in the background in case the user might need it
> > since I can predict what they might do relatively easily.
>
> I cache the items I'm displaying in an STL vector (C++). If the user moves
> to a page where I have no data I load it from the database as needed. I was
> considering loading data in the background in case the user might need it
> since I can predict what they might do relatively easily.
Pref
Thank you for your thoughts.
> You can build the result set into an array, then step through, back and
> around the array.
>
> SQLite already provides this functionality:
> http://www.sqlite.org/capi3ref.html#sqlite3_get_table
Having the entire result in memory would be an easy solution but unfo
On 7/25/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Any thoughts/brainstorming would be great from anyone :)
>
> Personally I don't have much experience with programming a database and
> the theory in it. But I suppose that in order to be able to go backward,
> the results already iterated
On Sun, 24 Jul 2005, Kim Bendtsen wrote:
>Hi There
>
>After executing a query I get the result back and can traverse it using
>sqlite3_step. This is fine for most systems, however for what I wish to use
>SQLite for, I would need something similar to stepForward, stepBackward,
>stepToFirst, stepToL
> Hi There
>
> After executing a query I get the result back and can traverse it using
> sqlite3_step. This is fine for most systems, however for what I wish to
> use
> SQLite for, I would need something similar to stepForward, stepBackward,
> stepToFirst, stepToLast.
>
> The application where I'm
6 matches
Mail list logo
