Associations are only marked as dirty if they contain dirty objects
Reported by Sam Smoot | October 4th, 2007 @ 02:51 PM
Right now a "clean" object won't trigger Association#dirty?. ie:
zoo = Zoo.first
zoo.exhibits << Exhibit.first
Since nothing was modified on the exhibit in this example, and Exhibit#dirty? will return false, then Association#dirty? will return false. Which is incorrect. Whenever an object is added or removed from an association it should be marked as dirty.
Comments and changes to this ticket
-
Sam Smoot October 22nd, 2007 @ 05:06 PM
Since BelongsTo assigns the foreign_key id, this actually seems to be a non-issue. I specced it anyways.
-
Sam Smoot October 22nd, 2007 @ 05:06 PM
- State changed from “open” to “resolved”
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
- Nobody is watching this ticket.
Referenced by
-
1385
rails3 with cache_cache classes = false causes problems with many 2 many associations
Classes are auto loaded: Article (obj #1), Person (obj
#2...
-
1
"Get DataMapper" web page
(from [f29d99b65ce0744f2d7e67f5663b30728b741b82])
Merge p...