Rails - Apr 2006 - Is caching in rails broken or at least very flawed?

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?

-- 
Posted via http://www.ruby-forum.com/.

Without a specific reason, it is tough to answer your question.  I have used
caching in several apps without any issues.

On 4/8/06, charlie bowman <cbowmanschool@yahoo.com>
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?
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>


--
Ben Reubenstein
http://www.benr75.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060408/433b1e33/attachment-0001.html

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..

-- 
Posted via http://www.ruby-forum.com/.