[ActiveRecord] How to avoid touching a class more than once in a reference hierarchy

say there are AR classes (omitted < ActiveRecord::Base):

class Project

class Member
  belongs_to :project, touch:true

class Todolist
  belongs_to :project, touch: true

class Todo
  belongs_to :todolist, touch: true
  belongs_to :member, touch: true

When I save a Todo instance, referenced Project instance will be touched
Is there any way to avoid this?

Appreciate for help. And sorry if my English is broken.

On 10 January 2013 08:03, Snow H. [email protected] wrote:

belongs_to :project, touch: true
Is there any way to avoid this?
First a question, will the todolist and member that a todo belongs to
always belong to the same project? So rather than being one project
touched twice it may be two separate projects?


This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs