I’ve walked through the “Resolving Conflicts” documentation have struck the following problems.
- The method outlined for creating the conflict from the documentation doesn’t create any documents with the “_sync:rb” problem.
I successfully implemented the algorithm for resolving the conflict and it resolved the conflict for the test scenario from the documentation.
-
It also detected the conflict for our application and “resolved” it - but it doesn’t seem to do anything about deleting the “_sync:rb” documents. They are still existing within the database and are still causing problems for our application.
-
There doesn’t seem to be any visible linkage between the “_sync:rb” documents and the application document. They don’t share the same ID or revision numbers. I know it’s the same document by looking at other attributes in the document, but I can’t see how CB is maintaining any linkage between the documents.
I’m still stuck with the same problem of these “_sync:rb” documents cluttering up the database. I could just do a brute-force delete on them, but that seems wrong. Any help appreciated, and thank-you in advance.