I've found that the best trade-off in performance and memory for on-demand
loading is to first run a query which retrieves all the id's of the items
you want in the list and store the list in memory. Then you can use that to
run a second query for full data using a where clause with "ID IN (...)"
Olaf Beckman Lapré <[EMAIL PROTECTED]>
wrote:
My question centers on how to implement this using SQLite as I'm not
really sure how to retrieve 'record numbers 445 to 456' using SQL
statements efficiently.
The simplest approach:
select * from tableName limit 12 offset 445;
This is actually not
Hello,
I'm looking for some advice on implementing 'On Demand Loading' in my program.
Some GUI controls such as a Listview have a 'virtual mode' where the control
only needs to be loaded with the items currently shown. The Listview will call
a callback function where it indicates which items ne
--- Liam Healy <[EMAIL PROTECTED]> wrote:
> Can you explain why you would want it to not compile as a
> loadable module? (i.e. under what circumstances you would not define
> COMPILE_SQLITE_EXTENSIONS_AS_LOADABLE_MODULE).
When you don't want the overhead/hassle of using shared libraries
and you j
Can you explain why you would want it to not compile as a
loadable module? (i.e. under what circumstances you would not define
COMPILE_SQLITE_EXTENSIONS_AS_LOADABLE_MODULE).
On 9/28/07, Joe Wilson <[EMAIL PROTECTED]> wrote:
> --- Liam Healy <[EMAIL PROTECTED]> wrote:
> > Thanks. I have included y
--- Liam Healy <[EMAIL PROTECTED]> wrote:
> Thanks. I have included your changes in extension-functions.c so now
> sqlite3_load_extension is usable. I had been using
> sqlite3RegisterExtraFunctions which is not the official interface, and
> that is why I never encountered this problem. Also, I h
Thanks. I have included your changes in extension-functions.c so now
sqlite3_load_extension is usable. I had been using
sqlite3RegisterExtraFunctions which is not the official interface, and
that is why I never encountered this problem. Also, I have improved
the Mac OSX instructions for those th
The BEGIN IMMEDIATE only locks the source database so that its contents
will not change while the copy is in progress. The fact that the other
databases are read-only means that they do not need to be locked against
changes, but they do need have some form of synchronization so that
existing re
[In the message "Re: [sqlite] 1-way replication best practices?" on Sep 28,
11:29, Dan Kennedy writes:]
> On Thu, 2007-09-27 at 14:26 -0700, Cyrus Durgin wrote:
> > hi,
> >
> > i'm using sqlite3 in a small project that will run on multiple servers.
> > only one of the instances will be read-write
9 matches
Mail list logo
