How to use it with cache sweeper?

[phuongnd08]

If I want to invalidate a cache when a model is created, how would I do it?

[dhh]

Call #touch on whatever you've made that cache depend on. See key-based expiration.

[phuongnd08]

Okay, I guess my case is a little special:
So I make a cache like this:

- cache 'testimonials' do
  = render 'testimonials', :testimonials => Testimonial.approved

We implemented a sweeper to make a call to expire_fragment('testimonial') when a testimonial is changed. But as far as I tried, expire_fragment doesn't work (because the cache key 'testimonial/'?)

[dhh]

Cache digests is not intended to work with manual expiration using a sweeper. Only key-based expiration.

On Nov 24, 2012, at 9:24, phuongnd08 notifications@github.com wrote:

Okay, I guess my case is a little special:
So I make a cache like this:

cache 'testimonials' do = render 'testimonials', :testimonials => Testimonial.approved
Inside the testimonials template, we fetch all approved testimonials using: Testimonial.approved and render each of them. We implemented a sweeper to make a call to expire_fragment('testimonial') when a testimonial is changed. But as far as I tried, expire_fragment doesn't work (because the cache key 'testimonial/'?)

—
Reply to this email directly or view it on GitHub.

[phuongnd08]

Are you saying expire_fragment work without cache_digests but won't work with cache_digests?

[dhh]

Correct. They are not designed to work together. Cache digests are only intended to work together with key-based expiration where you never need to manually expire and know the whole cache key.

There's a pull request available for turning off the digest on a per-call basis pending, though.

On Nov 25, 2012, at 7:05, phuongnd08 notifications@github.com wrote:

Are you saying expire_fragment work without cache_digests but won't work with cache_digests?

—
Reply to this email directly or view it on GitHub.