Well, it gives a more verbose explanation with an example. What would you
like it to say?




From:	Mike Rhodes <notifications@github.com>
To:	cloudant/CDTDatastore <CDTDatastore@noreply.github.com>
Cc:	Adam Cox <gadamc@cloudant.com>
Date:	05/29/2014 03:39
Subject:	Re: [CDTDatastore] 27991 conflicts v1 (#22)



In Classes/common/CDTConflictResolver.h:


> + * (via calls to CDTDatastore methods). Doing so will create a blocking
transaction to
> + * the database, the code will never excute and this method with hang
indefinitely.
> + *
> + * Finally, if nil is returned by this method, nothing will be changed
in the database and the
> + * document will remain conflicted.
> + *
> + * @warning Note that CDTDocumentRevision is an immutable object. Until
the development of
> + * CDTMutableDocumentRevision is complete (on the roadmap to be
completed soon), implementations should choose
> + * a particular revision in the conflicts array to be the winner and
return that object.
> + * Additionally, due to this restriction, documents may not yet be
deleted with this conflict resolution mechanism.
> + * (A work-around would be to delete the current winning revision in
multiple calls to
> + * [CDTDatastore getDocumentWithId:error:] until no winning revisions
are found.)
> + * The future CDTMutableDocumentRevision will provide a flexible way of
merging conflicts.
> + *
> + * @bug WARNING: Currently (20 May 2014), this does not properly migrate
attachments for resolutions that
> + * choose revisions that are not the current winning revision. See
CDTDatastore for details.



Does CDTDatastore really provide more details on this problem?


—
Reply to this email directly or view it on GitHub.