Good morning everybody.
We recently faced this problem.
We have a web application + mobile android application. The web application communicate directly with the CB server using the SDK and the mobile application with CBLite and SG.
Everything pretty straightforward.
We are looking to a FIXED ID document A
- The document A exists and it’s sync to the mobile device
- From the Web Application we delete the document A using the SDK running the query “DELETE FROM BUCKET USE KEYS ‘A’”
- The document has been deleted to the server, and the deletion revision has been sent to the mobile device. The document is deleted everywhere
- Now the “issue”
from Web Application we create again the document A, through the SDK, using the “INSERT INTO” (same issue with UPSERT) statement.
- The document has been re-created, with revision 1, and it’s NOT propagated to CBLite (because it has a revision 2, the deletion inside)
I was expecting, the second time I recreate the document the revision should be 3. We already found another approach to solve our problem, but I would like to know if it’s something obvious that the second time the revision is still 1 or it’s something we might need to discuss about.
Thanks for any feedback and have a good day.