[Question] Programmatically Clear Entire Cache about graphql-ruby-fragment_cache HOT 7 CLOSED

Amazing library by the way! So helpful over caching entire queries.

from graphql-ruby-fragment_cache.

Hey @jakemumu! It depends on the storage you use: for instance in Redis you can remove all keys starting with graphql/

from graphql-ruby-fragment_cache.

For sure -- I noticed however when using no memory store in local development, it defaults to its internal memory mechanism. I haven't seen a way to disable or clear this one when working locally? Apologies if it's there.

from graphql-ruby-fragment_cache.

You can clear a memory one as well (.clear, here) but I'm not sure if it's possible to connect to the running process from the console. Memory story is just a hash in the memory of a running process 🙂

from graphql-ruby-fragment_cache.

BTW, what problem are you solving? Maybe we can try an alternative solution

from graphql-ruby-fragment_cache.

I think I've made an idiotic mistake 0.o -- I have some bulk edits I've been making and checking on the API while working locally, I noticed I wasn't able to clear the cache, but I've just realized... simply restarting the rails server will dump the in memory cache! derp! -- totally can close this, idk how I didn't think of that

from graphql-ruby-fragment_cache.

Indeed, restart will definitely drop the cache 😅But in production we should make sure to prefer something that persists, otherwise we'll have weird performance while cache is warming. Please ping me if you need anything else!

from graphql-ruby-fragment_cache.