I took a look at the code. My perception is that, while the new design *can* imnplement what I want, it cannot do so without writing code at the C level. since I am using sqlite via the dll "wrapper", I do not have this option, I would need an "api" level capability for this, which is not the same thing as the new virtual OsFile.
> -----Original Message----- > From: Will Leshner [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 01, 2005 2:46 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Feature request > > > On Nov 30, 2005, at 4:18 PM, Cariotoglou Mike wrote: > > > The concept of in-memory database would be greatly enhanced > if there > > was a mechanism to serialize the internal cache to/from a > stream (not > > necessarily a disk stream). In-memory databases are > extremely useful > > for a number of applications, but ar a PITA to initalize/persist. > > With the very exciting virtual OsFile API that is being > developed, I'm wondering if we couldn't serialize a SQLite > database ourselves. I haven't looked at the entire API, so > maybe this isn't possible, but if you can create multiple > "subclasses" of OsFile in the same application, then you > could have an on-disk subclass for your file system, and an > in-memory one as well, and theoretically SQLite wouldn't know > the difference. Then you could attach one to another and copy > tables back and forth. > > >
