writing to a file is indeed the easy way, but I would rather not involve the filesystem if possible. yet, I guess that will be the way I will choose at the end. I also had a look at VFS, but an easier method would have been better of course.
On Thu, Nov 29, 2012 at 2:53 PM, Eric Minbiole <[email protected]> wrote: > As a first (simple) approach, I might use the standard backup API to back > up to a temp file, then stream that file byte by byte over the > communication protocol. > > I'm sure there may be other more direct-to-memory approaches, perhaps using > a custom VFS. However, this approach should be simple and easy, and would > not require any special serialization library-- just standard file I/O. > > > On Thu, Nov 29, 2012 at 8:19 AM, Map Scape <[email protected]> wrote: > > > Hi all, > > > > I have an in-memory sqlite database which I want to convert to a simple > > char array, to send over a communication protocol. I want to do this > > preferably without using any serialization library. > > > > Basically I want to do what backup api calls does, but instead of copying > > database to another database, I will be copying it to a char > > array/string/stream (whatever you may call it). > > _______________________________________________ > > sqlite-users mailing list > > [email protected] > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
