Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dirty tracking and save callbacks #142

Open
samlown opened this issue Apr 19, 2012 · 1 comment
Open

Dirty tracking and save callbacks #142

samlown opened this issue Apr 19, 2012 · 1 comment
Labels

Comments

@samlown
Copy link
Member

samlown commented Apr 19, 2012

Save callbacks are not triggered when save is called unless something in the model has changed. This is incorrect, dirty tracking should only limit sending data to the server, not the save process itself.

Setting the disable_dirty attribute to true on the model before the save is called gets around this issue:

def active=(value)
  self.disable_dirty = true
  @active = value
end

sam

@jayniz
Copy link

jayniz commented Sep 17, 2013

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants