-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/31/2011 07:49 AM, Simon Slavin wrote: > neither of them can enter the new price into the system, they have to each > enter the price change,
You cannot get conflicts if both "users" are talking to the same server - I can explain why if you care. If they are using different servers then both can modify the same document setting a new value and the conflict resolution system will pick one of them as a winner. Programmatically you can then find out there were conflicts and what they were - some you can automatically merge and others would require appropriate action. > Except that there's no language provided to figure out the '5'. So it has to > be done by your language. Which is the same problem SQLite has. So CouchDB > has no advantage here. If the price is made up of multiple components then a language does indeed have to calculate the final value. This is usually done by map/reduce and both CouchDB and MongoDB do that server side using Javascript (ie they have a builtin Javascript environment). CouchDB also allows other language servers too (eg there is a Python one). SQLite has no library level language other than very limited SQL. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk41eKUACgkQmOOfHg372QQAXwCgwLltQHR6rkZTgcQjhPWlhL28 A/0AoM1UsiJ0oyy5iv3mirocJ6kV2lN+ =ihZB -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
