Thank you very much for your suggestion and for digging up that blog post.
I'm glad I wrote it :)
I'm really reluctant to add this functionality out of the box for the
reasons mentioned in the post, even as a configurable opt-in option.
UpdatableRecord is already governed by many options, each of which
contributing to more complexity.
What looks really simple in the context of a store() call needs to be
viewed in a more global context, e.g. when passing a Record to an Update
statement through set(Record), and in many other parts of the API. In fact,
you're not really looking for a change of store() behaviour, but for a
change of changed() behaviour.
However, I think it should be easy for you to work around this issue by
implementing a RecordListener, that would reset "unmodified" fields prior
to calling store().
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].