Or...if that I'd too advantages... How about if said union. Function is called with an with a URL param on reads that merges the docs.... And if a union succeeds it returns in the header x-couch-merge: revision or something like that...that way you know a union just occurred and you can delete the others or something On Sep 17, 2014 10:42 PM, "Stanley Iriele" <[email protected]> wrote:
> Or....a conflict is only saved as a conflict of this function returns > null.. Saying " idk how to resolve this so leave it as a conflict " > On Sep 17, 2014 10:39 PM, "Stanley Iriele" <[email protected]> wrote: > >> Hey, >> >> This idea I'd still in the rough so bear with me a little. Couchdb is an >> ap system... And stores the result of both docs during a conflict. We have >> update functions as a way to do incremental updates. And show functions to >> do a transform on a doc before sending it. Can we have union functions to >> resolve a conflict between 2 docs?... >> >> This function would only run in the case of conflicts... And perhaps >> there can only be on per database or something idk... But the basic idea is >> that it takes (doc, doc) along with say...vector clocks or >> something....and the returned doc is saves to disk...or rather..the non >> returned value is removed from the revision tree. The exact logic is a >> little shaky bit the idea is pretty solid... Thoughts? This would be >> incredible....if properly designed >> >
