> So you can copy any block of memory you have a handle for into that, use > SQLite to manipulate the data while it's in memory
Simon, could you elaborate what you meant by that. To my knowledge you can't just copy any block of memory into SQLite and make it treat this memory block as database. Did you meant something else? Pavel On Tue, Jul 19, 2011 at 9:54 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 19 Jul 2011, at 5:55am, Glenn McCord wrote: > >> I've just had a quick look at the backup API, and it seems to make use >> of filenames and sqlite databases, which is not exactly what I'm >> after. > > SQLite has a pseudo-filename of ':memory:' which refers to a database kept > entirely in memory. So you can copy any block of memory you have a handle > for into that, use SQLite to manipulate the data while it's in memory, then > use the backupAPI again to copy the results back to some memory you then > write to your MPEG4 file. > > But I think in the meantime others in the thread have come up with better > suggestions for you. > > Simon. > _______________________________________________ > 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
