Yes, I thought about getting the conflict state while querying multiple
documents, event without the include_docs=true. It would be interesting
to see how expensive such a request would be.
Alternatively a cheap way would be to flag a document as 'possibly
conflicting' when a branch is created (i.e. an update made on the same
revision) -- or isn't it just the case: merges are not done
automatically, are they?.
Eric.
I'm not sure if you mean getting the conflict state without getting the
entire document (i.e. without include_docs=true). It would be possible, but
I don't know how expensive it would be. Perhaps couchdb would have to do as
much tree walking to find the conflicting revs as it would to retrieve the
entire document anyway.
Regards,
Brian.
