> On Oct 29, 2014, at 8:58 AM, Scott Ahten <[email protected]> wrote:
>
> Looking at the code, it's always calling createRevision on the revision we
> want to keep, then saving it's new revision, even if the revision from the
> enumeration is not the current revision. Should it be creating a new revision
> with the actual conflicting revision returned in the enumeration, then saving
> that instead?
Aw crap, you're right — it's a mistake in my sample code. The line
CBLUnsavedRevision *newRev = [current createRevision];
should be
CBLUnsavedRevision *newRev = [rev createRevision];
which I think is the same change you made in the code you just posted.
I'll go fix the docs again. Thank you so much for noticing & debugging this.
—Jens
--
You received this message because you are subscribed to the Google Groups
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/mobile-couchbase/9A54F701-FE25-4EFB-9A00-E8F411794178%40couchbase.com.
For more options, visit https://groups.google.com/d/optout.
