Cache invalidation

278 views
Skip to first unread message

Adam Fields

unread,
Jul 13, 2010, 9:52:43 AM7/13/10
to mon...@googlegroups.com
I see the mongoid extra to use caching, but I don't see anything about
how the cache gets invalidated or expired. How does this work? Is
there any way to invalidate the cache?


--
- Adam
----------
If you liked this email, you might also like:
"Some iPad apps I like"
-- http://workstuff.tumblr.com/post/680301206
"In praise of the Sous Vide Supreme"
-- http://www.aquick.org/blog/2010/05/17/in-praise-of-the-sous-vide-supreme/
"Just Married!"
-- http://www.flickr.com/photos/fields/4721009476/
"fields: @wwwmarty http://www.mvps.org/winhelp2002/hosts.htm"
-- http://twitter.com/fields/statuses/18367598768
----------
** I design intricate-yet-elegant processes for user and machine problems.
** Custom development project broken? Contact me, I can help.
** Some of what I do: http://workstuff.tumblr.com/post/70505118/aboutworkstuff

[ http://www.adamfields.com/resume.html ].. Experience
[ http://www.morningside-analytics.com ] .. Latest Venture
[ http://www.confabb.com ] ................ Founder

kshet26

unread,
Aug 5, 2010, 2:05:02 PM8/5/10
to Mongoid
I too am looking for an answer on this.

On Jul 13, 9:52 am, Adam Fields <fie...@street86.com> wrote:
> I see the mongoid extra to use caching, but I don't see anything about
> how the cache gets invalidated or expired. How does this work? Is
> there any way to invalidate the cache?
>
> --
>                                 - Adam
> ----------
> If you liked this email, you might also like:
> "Some iPad apps I like"
> --http://workstuff.tumblr.com/post/680301206
> "In praise of the Sous Vide Supreme"
> --http://www.aquick.org/blog/2010/05/17/in-praise-of-the-sous-vide-supr...
> "Just Married!"
> --http://www.flickr.com/photos/fields/4721009476/
> "fields: @wwwmartyhttp://www.mvps.org/winhelp2002/hosts.htm"
> --http://twitter.com/fields/statuses/18367598768

Durran Jordan

unread,
Aug 5, 2010, 4:32:24 PM8/5/10
to mon...@googlegroups.com
It's not a true cache in that sense - all it does is keep the
documents in memory if a single query has multiple iterations
happening on it... Otherwise it will hit the database again for each
iteration.

The next criteria that is created and hits the db would be a fresh hit...

Reply all
Reply to author
Forward
0 new messages