Comments and changes to this ticket

During our discussion, I asked Sam something along the lines of: "If we say that associations should be tracked in memory even if the related models are not saved to the database, are we not moving in the direction of tracking all unsaved models in memory? If so, does that mean we are moving down the 'slippery slope' to the point where we expect the following" (Sam's example): @cow = Cow.new; Cow.all.entries.should include(@cow)

Sam had written earlier that the behavior he wants to see is: @cow = Cow.new; Cow.all.entries.should_not include(@cow)

Sam wrote: "the difference is that in [the in-memory specs] you're not using a finder. You're making an explicit assignment. Even if one side was saved and a finder was issued on the association load, it should still contain the item(s) you explicitly added. ... so I think the line for me is that finders don't go out and find unsaved data. But association methods shouldn't clear out assigned data when their finder is triggered.""