On Tue, Sep 01, 2009 at 01:46:03PM -0500, Jeff Godfrey scratched on the wall:
> The issue lies in my starting point. The persistent storage of my
> SQLite database file isn't as a separate, disk-based file as it would
> normally be. Instead, it's stored as a stream inside a "container file"
Joe,
Thanks for the response, and sorry for not being clear on my work flow.
Ultimately, I want to access a standard SQLite database "in-memory".
Starting with a disk-based SQLite database, I can easily replicate it
into a memory-based database and access it from there. That's not a
On Tue, Sep 01, 2009 at 08:30:56AM -0500, Jeff Godfrey scratched on the wall:
> Hi All,
>
> I have a C# application that uses the System.Data.SQLite assembly for
> SQLite access. The ultimate goal is to access the SQLite data as an
> in-memory DB. Prior to access though, the database file
Jeff,
I'm not sure if I completely understand your intended work flow, but in
these cases I'd generally try to work with data like this via a
memory-mapped mechanism, especially relevant when you know the size of the
data object in question ahead of time, as you apparently do, once a
streaming
Hi All,
I have a C# application that uses the System.Data.SQLite assembly for
SQLite access. The ultimate goal is to access the SQLite data as an
in-memory DB. Prior to access though, the database file itself has to
be retrieved from a "container storage mechanism", as it's not stored
5 matches
Mail list logo
