On Tue, 2009-09-08 at 09:45 +0200, Marian Aldenhoevel wrote: > C) A silly idea. > > I could also split the database file into two copies. > If the readers can tolerate data that is one update behind currency then you could use two database files and have the reading program(s) switch to the other database after each round of updates.
In the background apply the same updates to the off-line copy. No need to copy the database entirely except at the very start of use. By choosing the number of updates to make in each cycle you have the possibility to limit the degree of "out of date". _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
