It is not possible to rewrite cacheTime when using queryClient.setQueryData

[joseucarvajal]

I'm iterating through a result array and using setQueryData to memoize individual results. I also have a specific hook to fetch these results individually with userQuery(...). I've tried to set the cacheTime other than 5 mins and it's been not possible when using setQueryData. I've tried many different approaches:

1. set cacheTime as configuration in queryClient.setQueryData(['task', id], data, {cacheTime:5000})
2. set cacheTime within the specific hook with the userQuery(['task', id], fetchFn, {cacheTime:5000})
3. queryClient.setQueryDefaults(['task', id], data, {cacheTime:5000})

None of them have worked, cacheTime always is 300000 when using querClient.setQueryData.

I'm working with react-query v3.13.10.

[TkDodo]

Not sure what issue you are trying to solve, what’s your use case? setQueryData can set the query data, not query options.

However, number 2 in your list should work. useQuery accepts a cacheTime option: https://react-query.tanstack.com/reference/useQuery

[joseucarvajal]

Thanks @TkDodo,

The issue I’m facing, is that I haven’t been able to set cacheTime when using setQueryData(...). This is my question: Is there any way to set cacheTime when using useQueryData?.

[TkDodo]

if that's the question then the answer is: no, it's not possible.

but I don't think that is the question. You're clearly trying to solve a problem by setting cacheTime via setQueryData, and I would like to know what that use-case is. Maybe there is a completely different way of solving that problem that doesn't have anything to do with setting cacheTime via setQueryData. But you need to describe your problem in order for me to help out here :)

[thongtv-1835]

@TkDodo I try to apply react-query in my company project, just for learning how to use it.
We have an event list on home page. And when the user choose a specific event, all other data of other screens will change depend on it. And when the user choose an event, I will save that id in queryClient (cache time = Infinity). Is it possible?

[TkDodo]

well choosing an event by the user looks like client state to me - owned by the user, not by a backend. So it seems like you want to store that in some client-side state manager

[thongtv-1835]

@TkDodo Yeah I got it. Thank you 👍

[thongtv-1835]

@TkDodo But I think It would be useful if we have options for queryClient .setQueryData like useQuery. Do you plan to support that in the future?

[TkDodo]

setQueryData only sets data, I don't see why it should set anything else 🤔

[joseucarvajal]

It would be awesome if serQueryData had the option to set data duration on cache memory.

…

On Mon, Aug 9, 2021 at 7:48 AM Dominik Dorfmeister ***@***.***> wrote: setQueryData only sets data, I don't see why it should set anything else 🤔 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2146 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKCJP52R3JPKVHQE7OTOCDT37FCVANCNFSM5BZT7PFQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[TkDodo]

you can do that with queryClient.setQueryDefaults for your specific key, or via queryClient.setDefaultOptions for all queries