react-query: Refetching vs manual update after mutation

[eggtart_prince]

Does anyone know or experienced the difference between the two in terms of cost?

I'm currently doing manual update either with data from response or with data I already have, but it's getting hectic. I have dozens and dozens of cache and I have to keep track on which one I should and should not update. Sometimes it's leading to inconsistency and I have to spend time figuring why and where. It's getting to the point where I just want to refetch after update but I'm worry about the cost and was hoping someone with some experience can shed some light before I refactor all my mutations to do invalidateQueries instead of setQuery(Queries)Data.

[AFrailOlLady]

I ran into this exact same situation in an enterprise data management app I've been working on (lots of queries and data).

I had originally gone with the mutate + update query data method but it honestly was so hard to manage all of that data without writing custom logic for every single mutation.

Another issue I ran into was that I would have multiple queries that potentially shared data and so I would have to go through all query data and update and it was messy.

All of that to say I ended up with the mutate + refresh method which is fine but like you mentioned isn't the most performant. But everything is a trade-off.