Commits on May 26, 2024

1. When consistent modify/delete operations get chunked, the additional … …

   …chunks will be flagged with with "isAdditionalChunk" so that consistent operations are never applied multiple times on the sync server.
   
   For delete operations, this is only an optimisation, since executing the deletions several times based on given criteria is not an error.
   
   For modify operations, this was not an issue until we added PropModifications.
   
   PropModifications can make mathematical addition and subtraction and those operations must not be done twice if consistency shall be waterproof.
   
   If a query such as: db.people.where('name').startsWith('A').modify({
     age: add(1)
   });
   ...and there happens to be 1000 local people matching the criteria, those people would end up getting their age added not with 1 but with 5 if modifyChunkSize is 200 since the operation would result in 5 mutations of 200 each - all with criteria and changeSpec in them. When reaching the server, it would ignore the changes that the client computed and instead run the criteria on its database and execute the addition 5 times - one for each chunk. With this commit, all but the first chunk will be flagged with isAdditionalChunk=true, making the server only execute the consistent operation on the initial chunk and ignore the rest. However, the keys of the remaining chunks are still important information for server, so are the local results that came out from it

   

   dfahlander committed May 26, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for f13dfd3
   • Browse repository at this point

   Copy the full SHA

   f13dfd3 View commit details

   Browse the repository at this point in the history