diff options
| author | Sean Griffin <sean@seantheprogrammer.com> | 2015-09-28 16:17:08 -0400 |
|---|---|---|
| committer | Sean Griffin <sean@seantheprogrammer.com> | 2015-09-28 16:26:50 -0400 |
| commit | fb03a9ab35ed22e569ec9cef8a50ef72754b5dbe (patch) | |
| tree | 6a3bd9b1b02e35f452c8158544a8748d7a6ec301 /activerecord/test/migrations/to_copy_with_timestamps | |
| parent | e950c4b4a503d801ac141c143171dbffe758e6eb (diff) | |
| download | rails-fb03a9ab35ed22e569ec9cef8a50ef72754b5dbe.tar.gz rails-fb03a9ab35ed22e569ec9cef8a50ef72754b5dbe.tar.bz2 rails-fb03a9ab35ed22e569ec9cef8a50ef72754b5dbe.zip | |
Separate `dup` from `deep_dup` in the attributes hash
I'm looking to move towards a tree-like structure for dirty checking
that involves an attribute holding onto the attribute that it was
created from. This means that `changed?` can be fully encapsulated on
that object. Since the objects are immutable, in `changes_applied`, we
can simply perform a shallow dup, instead of a deep one.
I'm not sure if that will actually end up in a performance boost, but
I'd like to semantically separate these concepts regardless
Diffstat (limited to 'activerecord/test/migrations/to_copy_with_timestamps')
0 files changed, 0 insertions, 0 deletions