Forum: Ruby on Rails Is caching in rails broken or at least very flawed?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
73606b1d1042de19056f3d59492b652f?d=identicon&s=25 Charlie Bowman (beachguy82)
on 2006-04-08 19:37
I was going to add caching to my applications, but everything that I've
found through google is about all of the problems everyone has had with
caching.  Is is really as bad as I've read?
D90ef6808433e63203e15a5c2dadb0bb?d=identicon&s=25 Ben Reubenstein (Guest)
on 2006-04-08 19:49
(Received via mailing list)
Without a specific reason, it is tough to answer your question.  I have
used
caching in several apps without any issues.
6f7c877de704c7cc03c8a3b2dc52df92?d=identicon&s=25 Carmen --- (carmen)
on 2006-04-08 19:58
charlie bowman wrote:
> I was going to add caching to my applications, but everything that I've
> found through google is about all of the problems everyone has had with
> caching.  Is is really as bad as I've read?

i've been curious about this as well. it seems if rails/AR was able to
magically divine whether a cached piece was out of date, it also would
be able to generate schema and we wouldnt need migrations. that and if
you have to do a query like 'order by updated_on desc limit 1' you might
as well fetch the data fresh, unless you are displaying 1000 records and
doing some slow regex on all of them..

i'm just a skeptic, but would love to hear some positive experiences..
This topic is locked and can not be replied to.