Description
There are some inconsistent behaviors b/w different APIs and b/w platforms.
CBL-C:
- Use same instance, creates a new deleted revision.
- [Conflict] Use different instance, creates a new deleted revision if lastWriteWins is selected.
- [Conflict] Use different instance, fails if failsOnConflicts is selected.
Other Platforms:
- Use same instance, create a new revision.
- [Conflict] Use different instance, loads deleted doc and replace current dod internally if lastWriteWins is selected.
- [Conflict] Use different instance, fails if failsOnConflicts is selected.
Considering that when using the same instance, a new revision is created, to be consistent, when using lastWriteWins, the new revision should be created as well.
Attachments
Issue Links
- relates to
-
CBL-3749 testDeleteAlreadyDeletedDoc may be off by one
- Closed