Forum: Ruby on Rails How key-based cache expiration works for has_many relationship?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Matthijs L. (Guest)
on 2013-04-13 20:13
(Received via mailing list)
As an opportunity to get my latest project so damn fast, I looked into
key-based cache expiration, also known as the Russion Doll approach to

There is something I don't understand.

"You deal with dependency structures by tying the model objects together
> updates."

So if you change a todo that belongs to a todolist that belongs to a
> project, you update the updated_at timestamp on every part of the chain,
> which will automatically then update the cache keys based on these objects

Okay, so the hierarchy is project -> todolist -> todo. Then a single
item, probably keeps track of its creator, right?

In Rails it could be declared like this:

class Project < ActiveRecord::Base

class Todolist < ActiveRecord::Base
  belongs_to :project, touch: true

class Todo < ActiveRecord::Base
  belongs_to :todolist, touch: true
  belongs_to :creator

# in app/views/project/show.html.erb
<% cache project do %>
  <p>All my todo lists:</p>
  <%= render project.todolists %>
<% end %>

# in app/views/todolists/_todolist.html.erb
<% cache todolist do %>
  <p><%= %>:</p>
  <%= render todolist.todos %>
<% end %>

# in app/views/todo/_todo.html.erb
<% cache todo do %>
  <p><%= %>(by <%= %>)</p>
<% end %>

# This will not trigger todo.touch!,
# which in turn does not trigger todo.todolist.touch!
# and does not trigger todo.todolist.project.touch!
todo.creator.update_attributes(name: 'John D.')

What do I need to change in order to make this process trivial to
caching schemes and trust that I am never going to serve stale data?
This topic is locked and can not be replied to.