On Apr 14, 2016, at 4:50 PM, Brendan Duddridge <[email protected]<mailto:[email protected]>> wrote:
Database: PUT _id=rec-a0ada90ce645458ebdb3ff7259c6fb1b, _rev=1-4098dccaa969cdbab64825e687aaec68, _deleted=1, allowConflict=1 Database: Duplicate rev insertion: rec-a0ada90ce645458ebdb3ff7259c6fb1b / 2-a106816d32bc283bc24acf98abeeec2d This is strange: it’s saying that the revision deleting rev 1-409 already exists, so the operation is a no-op. But if that’s true, then rev 1-409 isn’t a leaf, so it can’t possibly count as a conflict. I’m thinking now that there’s something wrong in the structure of the database — most likely that the `current` column of the row for rev 1-409 is mistakenly set to `1` when it should be `0`. Would it be possible for you to email me a copy of the database (the .cblite2 bundle)? —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/46F54D49-196A-4A40-AA93-833420389205%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
