-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/30/2011 03:31 PM, Alexey Pechnikov wrote: > There are no conflicts!
If you have multiple masters then incompatible changes can be made to the same data. > Two versions are two _different_ versions of the row. ie you have a conflict. > 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. And that is how *you* deal with conflicts for *that* data. What should be done depends on the semantics of the data without there being one right answer. Note that the administrator, the developers and the users are generally different people with different goals. > I think easy replication is not feature of NoSQL solutions. Replication is needed to ensure availability of a database and is mostly independent of other database characteristics. My original point was that CouchDB has multi-master replication builtin - you do not have to write extra code or do anything special. Multi-master replication is extremely rare for databases and is a great feature for some use cases. It also allows local offline access - a space where CouchDB overlaps with SQLite usage. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk40jZYACgkQmOOfHg372QTGWACfeMUJBSMSUxM7ORRzFJ0GxEsI vCEAn2G746/inANLxJYP4gLKrZcAW/Vx =lcau -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
