problem with updating an object in an association
Reported by matthewcford | August 1st, 2008 @ 11:35 AM
might be related to bug 446, when updating one object within an association, it updates the updated_at attribute for all other objects in the association.
Comments and changes to this ticket
-
Bernerd Schaefer August 1st, 2008 @ 11:58 AM
- Assigned user changed from “Sam Smoot” to “Bernerd Schaefer”
- State changed from “new” to “open”
This is unrelated to #446, which I just committed a fix for.
It seems that the updated_at/on fields get updated before save regardless of whether the resource is dirty, which means that any time you call save on an object it will be seen by DM as dirty, and will get updated in the database.
This will require a little bit of thought before handling, but once we reach a decision, won't be hard to fix.
-
Dan Kubb (dkubb) January 8th, 2009 @ 04:44 AM
- State changed from “open” to “accepted”
- Assigned user changed from “Bernerd Schaefer” to “Dan Kubb (dkubb)”
-
Jonathan Stott (namelessjon) February 22nd, 2009 @ 08:30 AM
- Tag changed from “associations, bug, dm-core” to “associations, bug, dm-core, one_file_test”
This is currently impossible to verify due to a bug in dm-timestamps
The attached one file test should verify the problem or no.
-
Dan Kubb (dkubb) May 28th, 2009 @ 04:13 AM
- State changed from “accepted” to “resolved”
I can confirm this is resolved in dm-core/next. Attached is a (slightly modified) version of Jonathan's script that demonstrates the fix.
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 »
Dan Kubb (dkubb)
Jonathan Stott (namelessjon)
matthewcford