2011/7/31 Roger Binns <rog...@rogerbinns.com>: > It takes more than a few lines of SQL. You've also got to be careful how > you write data (result is a DAG), you need replication code and you need > conflict resolution code.
There are no conflicts! Two versions are two _different_ versions of the row. Simple copy _all_ un-exists rows by SQL query with attached database or simple script http://sqlite.mobigroup.ru/wiki?name=sqlite3-rdiff It can be included into custom sqlite3 shell :) On application level we may show the last version of each record (and full history of record). And user can view and revert any changes. I think easy replication is not feature of NoSQL solutions. With big disks we can create and use append-only datasets in SQL DBMS. And virtual table can incapsulate all details. -- Best regards, Alexey Pechnikov. http://pechnikov.tel/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
