Hi Richard, Thanks for the advice: I will take a look into a barebones VFS implementation for backup purposes. I assume it won't need the usual locking functionality that normal VFS implementations require: pretty much just read, write, open and close?
What is the ETA for 3.6.11? Daniel > -----Original Message----- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- > boun...@sqlite.org] On Behalf Of D. Richard Hipp > Sent: Wednesday, February 04, 2009 3:19 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Saving and loading SQLite pages from a buffer > > > On Feb 4, 2009, at 6:09 PM, Brown, Daniel wrote: > > > > I currently use SQLite by opening ":memory:" and then copying the > > tables > > I want from read only storage into ":memory:" via an attached read > > only > > database, which I drop after copying is complete. My issue is saving > > and loading the ":memory:" database once I've used it and changed its > > contents after this initial creation. I cannot write the backup > > back to > > the file system as it is read only but I can potentially save and > load > > it via an API that saves and loads blocks of memory to a persistent > > memory location on my platform. > > > > So, create a VFS that instead of writing to disk, writes to the > persistent memory location on your platform. That backup to your > VFS. If the only operation your VFS supports is a backup, it can be > very simply - omitting much of the functionality found in a general- > purpose VFS. > > > D. Richard Hipp > d...@hwaci.com > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
