Theoretically, there could be such situation, when in sync storage table, we can find, Deletion of a document, and after that, creation of document with the same id. This raises two questions:
- is such situation possible in real world?
- should sync storage react to such situations and how?
+----+------+---------------+----------------------------------+---------------------+--------+
| id | type | document_type | document_id | timestamp | status |
+----+------+---------------+----------------------------------+---------------------+--------+
| 3 | C | product | id0 | 2015-01-22 15:20:25 | 0 |
| 4 | U | product | id0 | 2015-01-22 15:20:25 | 0 |
| 5 | D | product | id1 | 2015-01-22 15:20:25 | 0 |
| 6 | C | product | id1 | 2015-01-22 15:20:25 | 0 |
+----+------+---------------+----------------------------------+---------------------+--------+
Theoretically, there could be such situation, when in sync storage table, we can find, Deletion of a document, and after that, creation of document with the same id. This raises two questions: