Manually Clear Fragment Cache in Rails

ruby-on-rails-3 caching memcached
yellowreign picture yellowreign · May 4, 2012 · Viewed 16.7k times · Source

I'm using Memcached with Heroku for a Rails 3.1 app. I had a bug and the wrong things are showing - the parameters were incorrect for the cache.

I had this:

<% cache("foo_header_cache_#{@user.id}") do %>

I removed the fragment caching and pushed to Heroku and the bad data went away.

And then I changed it to: 

<% cache("foo_header_cache_#{@foo.id}") do %>

However, when I corrected the parameters, from @user to @foo, the old [incorrect] cached version showed again (instead of refreshing with the correct data).

How can I manually expire this, or otherwise get rid of this bad data that is showing?

Answer

yellowreign picture yellowreign · May 5, 2012

I ended up manually clearing the entire cache by going into the rails console and using the command:

Rails.cache.clear

Related questions

Rails.cache error in Rails 3.1 - TypeError: can't dump hash with default proc

I running into an issue with the Rails.cache methods on 3.1.0.rc4 (ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10]). The code works fine within the same application on 2.3.12 (ruby 1.8.7 (2011-02-18 patchlevel 334) [i686-linux], MBARI 0x8770, Ruby Enterprise Edition 2011.03), but …

Read More
Rails dev environment not updating html/css/assets even after restarting server

I've been developing a site in rails, everything going relatively smooth. Suddenly my changes to the views and assets no longer show up. I change a stylesheet or some html and reload my browser at http://0.0.0.0:3000 and nothing changes. So …

Read More
mongoid query caching

Rails' ActiveRecord has a feature called Query Caching (ActiveRecord::QueryCache) which saves the result of SQL query for the life-span of a request. While I'm not very familiar with the internals of the implementation, I think that it saves the …

Read More