dirty not always being unset on resource save.
Reported by mpd | October 3rd, 2009 @ 09:52 PM
I have no idea how to explain this well, but this script replicates it. The resource is still dirty after a save and reload. This seems to only be an issue when dealing with new records with associated records that are also unsaved, which is sort of contrived for an app, but has come up often in testing for me.
example script at http://gist.github.com/201082
Comments and changes to this ticket
-
Dan Kubb (dkubb) October 4th, 2009 @ 09:29 PM
- State changed from “new” to “resolved”
(from [6b9ab6d8b945b73308d99b0fbdc6f074902eb1d9]) A dirty sibling should not make a resource dirty
[#1076 state:resolved] http://github.com/datamapper/dm-core/commit/6b9ab6d8b945b73308d99b0...
-
Dan Kubb (dkubb) October 4th, 2009 @ 09:29 PM
(from [6b9ab6d8b945b73308d99b0fbdc6f074902eb1d9]) A dirty sibling should not make a resource dirty
[#1076 state:resolved] http://github.com/datamapper/dm-core/commit/6b9ab6d8b945b73308d99b0...
-
Dan Kubb (dkubb) October 4th, 2009 @ 09:29 PM
- Assigned user set to “Dan Kubb (dkubb)”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
People watching this ticket
Dan Kubb (dkubb)
mpd
Referenced by
-
1076
dirty not always being unset on resource save.
[#1076 state:resolved]
http://github.com/datamapper/dm-c...
-
1076
dirty not always being unset on resource save.
[#1076 state:resolved]
http://github.com/datamapper/dm-c...