Tags: tutao/tutanota
Tags
process delete before put when updating cache by multiple for missed EEs When syncing an e-mail moved from and back to a given mailSet in a different client, we send a DELETE event and a CREATE event for the same MailSetEntry id, as MailSetEntry ids are derived from mail ReceivedDate and mail id. With 5a8b1d8 we are putting/deleting instances into the cache by multiple after accumulating them, and in a given accumulation the temporal order of events is not respected. This resulted in us putting the MailSetEntry using the CREATE event, and deleting it right away because of the DELETE event. This commit fixes that by first doing the deleteMultiple calls and calling putMultiple for entityUpdates with valid instances. Co-authored-by: das <das@tutao.de>
PreviousNext