On Thu, May 14, 2015 at 6:58 PM, Peter Norwich <[email protected]> wrote: >>> I would recommend you to use your own field for tracking ancestry and >>> relations and not generate rev manually > > I don't see how it's possible to do this since new_edits:false expects > existing revision ID. > and there is no API to just ask CouchDB to generate rev for a doc.
If you want to update an existed document, than you should provide any revision for it. > I see previous discussion "Making conflict first class citizens" > (http://grokbase.com/t/couchdb/user/124jegc8kn/making-conflicts-first-class-citizens) > Does anyone know what is the conclusion ? > It seems to be *exactly* what I need. But I don't see how to do that now in > 2.0. > > new_edits:false seems too convoluted for what seems to be a simple task. > It's essentially asking developer to write CouchDB replicator (like PouchDB), > but my use case is just a lightweight desktop client (with no knowledge of > server DB), > pushes the doc, and resolve resulting conflict manually. So your case if about just blindly push bulk docs from time to time and not care about any conflicts they may produce? -- ,,,^..^,,,
