💎 Rails tip💎 Do you have slow queries in your controllers that even pagination doesn't solve? You can easily cache them (if you have a cache store set) using `fresh_when`. #ruby #rails #rubyonrails

Someone mentioned to me that it's actually using the browser cache. This means you don't even need to have a cache store set!

@websebdev Indexes solve slow queries 🙂

@websebdev 👍 This is very useful and has some gotchas if your app has super dynamic content (ie. not a CMS style app but a project management app with RT updates).

@websebdev fresh_when is one of the many helpers to work with ETags. This is a great way to cache but it should be done carefully because it's a cache you don't directly control and it can introduce inconsistencies you can't easily fix. You can't run Rails.cache.clear to fix it for example

@websebdev api.rubyonrails.org/classes/Action… I've not seen this before & this is awesome! Thank you @websebdev !

@websebdev The best part about this technique is how simple it is to implement. Rails has a solution for everything.

@websebdev Cache store? That’s just http caching 🙂

@websebdev Thank you so much! Every week I learn with your tweets!

@websebdev Awesome tip.

@websebdev Nice tip. How does it invalidates the cache, even the data has gone stale?