-----Original Message----- >The hot backup API has not yet been released. Look for version 3.6.11.
I will look forward to seeing that release! Is there anything I can do to help with the development? >If you open your database using the special name ":memory:" then it is >held entirely in memory with no duplication of pages (accept as >required to support ROLLBACK). Such a :memory: database is initially >empty, of course. So then initialize it from a file using the backup >API. 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. I guess I could implement an in memory VFS to use with the existing backup API but that seems more complicated than extending the backup API to accept save or load from a memory buffer. As I said I'd be happy to contribute some time to extending the back system to support this. Daniel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
