[ https://issues.apache.org/jira/browse/COUCHDB-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837480#comment-13837480 ]
Dale Harvey commented on COUCHDB-1950: -------------------------------------- This is something that can happen regardless of options to have conflicts true by default, its something I was planning to work on for PouchDB and make a patch for CouchDB if it worked nicely > ddoc-based conflict resolution > ------------------------------ > > Key: COUCHDB-1950 > URL: https://issues.apache.org/jira/browse/COUCHDB-1950 > Project: CouchDB > Issue Type: Improvement > Reporter: Nathan Vander Wilt > > This was discussed at CouchConf in Vancouver last month, but didn't see a > hook here I could refer to in another conversation, so… > It'd be great if a design document could include a conflict resolver > function, in the vein of other "app logic" handler hooks like > validate_doc_write. I imagine it would look something like either "function > (currentWinner, nextWinningestLoser, parent)" (simply called multiple times > if more than 2 leafs) or simply "function (arrayOfDocs, revisionHistor)" — if > it returns a document, that's the winner, if not the next design document in > line gets a pass at it. (Bonus: if it throws, the conflict stays no matter > what other resolvers say?) -- This message was sent by Atlassian JIRA (v6.1#6144)