Closed robmathews closed 13 years ago
The rails3 branch is totally f'ed and does not work in the least. I think the way forward is to fundamentally change the way cache money works for rails3 and instead extend the existing caching feature to use memcache instead of the in memory store.
If you would like to take a stab at get this branch running then go for it.
Ah, well at least it's not ambiguous ;)
I'm not actually sure that cache-money is a gem that should be ported into Rails3. I see new and better caching in Rails3, etc. Before I spend any time with it, I like some assurance that it's not replaced by some other Rails3 gem etc ... do you happen to know?
There are no assurances. I would rather that we not do cache-money for Rails3 and instead focus on a new GEM that extends the caching that is there.
Can you recommend similar gems for Rails3?
I liked cache-money because I don't have to write explicit fetch and invalidate data explicitly. I need a gem to use without changing my code and have to replace all finds with fetches.
Any thoughts/suggestions are appreciated.
There are two that I know of. I have not used either but orslumen has contributed before and writes solid code.
https://github.com/orslumen/record-cache https://github.com/csdn-dev/second_level_cache
Hi guys.
I was wondering what the state of the rails3 branch was. Last news I see is here: http://stackoverflow.com/questions/3794511/cache-money-for-rails-3 which suggests that it wasn't ready in October.
I like to take it out and play with it, but are the instructions accurate for Rails3? They seem unchanged since Rails2 ... that can't be right.