Be aware that the backup process will need to restart from zero after each write!
Now, if you can setup some kind of IPC between your two processes, then you could have the update process update the disk base and send identical data to the reader process, so the latter can update a memory copy. The two processe can run as fast as possible without much interference, as memory updates are very fast. The 50Mb is reasonable size for memory and would need loading only once at startup. For this to work, you have to take steps to insert identical fields including rowids, no randomblob or local timestamps. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users