{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/9c877363185e5f88c09aa28140c1a770?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"9c877363185e5f88c09aa28140c1a770","url":"https://api.github.com/users/noctivityinc","login":"noctivityinc","id":78850},"milestone":null,"assignee":null,"labels":[],"updated_at":"2011-10-29T20:38:35Z","closed_at":null,"comments":3,"url":"https://api.github.com/repos/cayasso/oomvc/issues/17","body":"I was able to do a work around for the other bug to move forward, unfortunately, the old out of sync bug now appears.\r\n\r\nWhen I go to update a line I inspect the line object in firebug and ALL attributes are there CORRECT, including the correct attribute names from the schema (i.e. entitySubType gets transformed back to type, which is right).  Here is the model RIGHT before the update is called:\r\n\r\nhttps://skitch.com/jlippiner/grxrt/mozilla-firefox\r\n\r\nBut when I inspect the POST that is occurring, as you can see it appears to be sending the OLD pre-db sync data AGAIN:\r\n\r\nhttps://skitch.com/jlippiner/grxra/mozilla-firefox\r\n\r\nSo none of the new attributes added after the initial create occurred as there, such as ID, causing the create.\r\n\r\nNot sure how or why the change you made in 0.1.7 broke the sync but please fix and let me know.","html_url":"https://github.com/cayasso/oomvc/issues/17","title":"BUG - update/save methods using out of sync data","number":17,"id":2086972,"created_at":"2011-10-29T13:38:04Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/9c877363185e5f88c09aa28140c1a770?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"9c877363185e5f88c09aa28140c1a770","url":"https://api.github.com/users/noctivityinc","login":"noctivityinc","id":78850},"updated_at":"2011-10-29T20:38:35Z","url":"https://api.github.com/repos/cayasso/oomvc/issues/comments/2566849","body":"FYI - I just tested 0.1.8-2 and bug #16 does appear fixed (i.e. the type is correctly returned) but this bug, #17, is still happening and is not fixed with the commit.","id":2566849,"created_at":"2011-10-29T20:38:35Z"}}