, 2007 5:35 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] Sharing an in-memory database between applications
Greetings!
We are using an SQLite database to store process data that will
eventually be displayed on a graph. The database design is simple,
including only six tables, but the table
an in-memory database between applications
Greetings!
We are using an SQLite database to store process data that will
eventually be displayed on a graph. The database design is simple,
including only six tables, but the table containing the data points for
the graph could contain a few million
Hi Rob,
On 7/13/07, Rob Richardson <[EMAIL PROTECTED]> wrote:
Greetings!
But I'm wondering if I can use an in-memory database to improve this
dramatically. The data is collected by a Windows service that collects
data and adds it to the database once a minute. If the service would
also store
Since Sqlite caches data in memory you are unlikely to achieve
spectacular improvements by having the database memory resident.
Perhaps you could investigate performing pre-processing of your data to
reduce the time it takes to render your graph.
Rob Richardson wrote:
Greetings!
We are using
Rob Richardson wrote:
that is much faster than a set of INSERT INTO
newtable SELECT * FROM oldtable (or whatever -- you get the idea)
statements.
The fastest way should be:
CREATE TABLE memdb.newtable AS SELECT * FROM oldtable
HTH,
Gerry
-
Greetings!
We are using an SQLite database to store process data that will
eventually be displayed on a graph. The database design is simple,
including only six tables, but the table containing the data points for
the graph could contain a few million records. By using the simplest
possible quer
6 matches
Mail list logo
