When I turn on Database logging this is what I get during conflict
resolution:
Database: Begin transaction (level 1)...
Tap Forms[29851:8985729] is deletion: 1
Database: PUT _id=rec-a0ada90ce645458ebdb3ff7259c6fb1b,
_rev=1-4098dccaa969cdbab64825e687aaec68, _deleted=1, allowConflict=1
Database: Duplicate rev insertion: rec-a0ada90ce645458ebdb3ff7259c6fb1b /
2-a106816d32bc283bc24acf98abeeec2d
Database: --> created {rec-a0ada90ce645458ebdb3ff7259c6fb1b
#2-a106816d32bc283bc24acf98abeeec2d DEL}
Tap Forms[29851:8985729] Saved new revision:
2-a106816d32bc283bc24acf98abeeec2d, parent: (null)
Database: PUT _id=rec-a0ada90ce645458ebdb3ff7259c6fb1b,
_rev=4272-a388b5ae2e82576f3bc56bfb1420c94e, _deleted=0, allowConflict=1
Database: Added: {rec-a0ada90ce645458ebdb3ff7259c6fb1b
#4273-fce7a57ef00a2a6a243c91b44cb1ade7}
Database: --> created {rec-a0ada90ce645458ebdb3ff7259c6fb1b
#4273-fce7a57ef00a2a6a243c91b44cb1ade7}
Tap Forms[29851:8985729] Saved new revision:
4273-fce7a57ef00a2a6a243c91b44cb1ade7, parent:
4272-a388b5ae2e82576f3bc56bfb1420c94e
Database: Commit transaction (level 1)
Database: CBLDatabase[<0x608000121900>db-1deccd0e15dc4047ab96eba344144f3b]:
Posting change notifications: seq 123627
Database: CBLDatabase[<0x6100001221c0>db-1deccd0e15dc4047ab96eba344144f3b]:
Notified of 1 changes by
CBLDatabase[<0x608000121900>db-1deccd0e15dc4047ab96eba344144f3b]
Database: CBLDatabase[<0x6180001258c0>db-1deccd0e15dc4047ab96eba344144f3b]:
Notified of 1 changes by
CBLDatabase[<0x608000121900>db-1deccd0e15dc4047ab96eba344144f3b]
Database: CBLDatabase[<0x6100001221c0>db-1deccd0e15dc4047ab96eba344144f3b]:
Posting change notifications: seq (123627)
Database: CBLDatabase[<0x6180001258c0>db-1deccd0e15dc4047ab96eba344144f3b]:
Posting change notifications: seq (123627)
Some of the messages are my own logging and I took out the timestamps just
so it wasn't so wide for this posting.
It just gets stuck in this loop spitting out the above messages over and
over.
Thanks,
Brendan
On Thursday, April 14, 2016 at 5:36:57 PM UTC-6, Jens Alfke wrote:
>
>
> On Apr 14, 2016, at 1:55 PM, Brendan Duddridge <[email protected]
> <javascript:>> wrote:
>
> Sorry, I meant to say "the new revision is getting its "isDeletion" flag
> set to YES".
> Maybe that's the problem? But I can't set the isDeletion flag unless I
> create a new revision it seems. So that 1-409 is never going away and I
> just keep creating new revisions over and over.
>
>
> 1-409 doesn’t go away but it acquires a child, 2-xxx, which is marked as a
> deletion. That means 1-409 is no longer a leaf, and 2-xxx is a leaf but
> it’s deleted so it doesn’t count as part of a conflict. The result should
> be no conflict.
>
> It sounds like the update of 1-409 isn’t taking effect somehow … weird.
>
> If you turn on logging for ‘CBLDatabase’ (or just ‘Database’, on the
> master branch) you'll get logs for newly created revisions. That might help
> figure out what’s going on.
>
> —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/e9b08599-5fcb-4613-b10a-ae0e142e4bd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
