Multiple mutations to the same collection
Does TanStack DB automatically handle multiple mutations like, for instance, an auto-save input field that sends a mutation
Is it able to cancel previous mutations or at least only keep the latest successful result, or do we have to handle that in application code? If so, are there any examples or best practices?
EDIT: Just saw this which looks promising https://github.com/TanStack/db/issues/35 - and makes me think the answer to my question is “no”.
But that then raises the question, out of curiosity: how do people using the default behavior handle this seemingly ubiquitous case? It seems like any mutation, unless you disable the UI while it’s running (though that wouldn’t really happen if you use optimistic updates), would face race conditions, no?
Take the following examples:
1. Adding a to-do: what if you add 3 to-dos very quickly, and the 2nd request completes faster for whatever reason (maybe the request ended up on a bad edge node?) - wouldn’t the to-dos in the UI jump around if you were sorting them by
2. Incrementing an item’s count in your shopping cart: if you’re sending the request as current+1, you sent the request 3 times, and the 2nd request won the race, you’d end up with a bad result, no?
onChangeIs it able to cancel previous mutations or at least only keep the latest successful result, or do we have to handle that in application code? If so, are there any examples or best practices?
EDIT: Just saw this which looks promising https://github.com/TanStack/db/issues/35 - and makes me think the answer to my question is “no”.
But that then raises the question, out of curiosity: how do people using the default behavior handle this seemingly ubiquitous case? It seems like any mutation, unless you disable the UI while it’s running (though that wouldn’t really happen if you use optimistic updates), would face race conditions, no?
Take the following examples:
1. Adding a to-do: what if you add 3 to-dos very quickly, and the 2nd request completes faster for whatever reason (maybe the request ended up on a bad edge node?) - wouldn’t the to-dos in the UI jump around if you were sorting them by
createdAt2. Incrementing an item’s count in your shopping cart: if you’re sending the request as current+1, you sent the request 3 times, and the 2nd request won the race, you’d end up with a bad result, no?
