There's no way to handle conflicts that way at the db layer. If you do a
GET with conflicts=true as outlined at
http://wiki.apache.org/couchdb/Replication_and_conflicts#Working_with_conflicting_documents,
you can get conflicting versions of the document hosted on the db, but that
doesn't do much for you at time of upload.
--David Tyler
On Thu, Jan 17, 2013 at 12:23 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:
> I'm trying to understand alternatives for handling update conflicts. Is
> there direct way to detect a conflict between two updates to the same
> document, and trigger a custom handler (as opposed to letting Couch's basic
> conflict resolution algorithm proceed, then undoing things after-the-fact)?
>
> Context: I'm trying to replicate the behavior of version control systems
> - i.e., on conflict, create a branch (two documents).
>
> Thanks,
>
> Miles Fidelman
>
> --
> In theory, there is no difference between theory and practice.
> In practice, there is. .... Yogi Berra
>
>
|