{"issue":{"milestone":null,"user":{"id":19878,"login":"jaryl","url":"https://api.github.com/users/jaryl","avatar_url":"https://secure.gravatar.com/avatar/c001a49670b21737ef0113b89074bc67?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"c001a49670b21737ef0113b89074bc67"},"title":"State transitions do not persist to DB in ActiveRecord models","created_at":"2009-04-25T20:27:40Z","labels":[],"updated_at":"2011-12-20T08:50:43Z","state":"open","id":7123,"html_url":"https://github.com/rubyist/aasm/issues/2","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"foo.bar! does not persist to the database due to a failed validation. The documentation for the WriteState::aasm_write_state method indicates that update_attribute is being used to bypass validation, but this is not the case.\r\n\r\nAfter calling write_attribute, save is being called to persist the changes. Since save does validation, this breaks the design of state transitions in AASM.\r\n\r\nA proposed fix would be to call save(false) to skip validation, see pastie:\r\n\r\nhttp://www.pastie.org/444480","number":2,"url":"https://api.github.com/repos/rubyist/aasm/issues/2","comments":10,"assignee":null},"comment":{"user":{"id":3209,"login":"alto","url":"https://api.github.com/users/alto","avatar_url":"https://secure.gravatar.com/avatar/60b2dcb6aa428cc94d11a8c9c1431edc?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"60b2dcb6aa428cc94d11a8c9c1431edc"},"created_at":"2011-12-20T08:50:43Z","updated_at":"2011-12-20T08:50:43Z","id":3216167,"body":"Okay, I see. If the state is not changed, then it's a bug, and I'll fix it soon.","url":"https://api.github.com/repos/rubyist/aasm/issues/comments/3216167"},"action":"created"}