aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases/arel/nodes
diff options
context:
space:
mode:
authorKasper Timm Hansen <kaspth@gmail.com>2018-07-01 12:42:18 +0200
committerKasper Timm Hansen <kaspth@gmail.com>2018-07-01 12:46:15 +0200
commit969577d960cd7e2d0a421af4a987f56894c3b229 (patch)
treeea6aa0f608aa255e0e49a6d0970baedf6dca92e5 /activerecord/test/cases/arel/nodes
parentf666fb58a3d7b56461d9aac04411022aaa86c0c7 (diff)
downloadrails-969577d960cd7e2d0a421af4a987f56894c3b229.tar.gz
rails-969577d960cd7e2d0a421af4a987f56894c3b229.tar.bz2
rails-969577d960cd7e2d0a421af4a987f56894c3b229.zip
Refactor #33254.
Firstly, increment and decrement shouldn't care about the particulars of key expiry. They should only know that they have to pass that responsibility on to somewhere else. Secondly, it moves the key normalization back inside the instrumentation like it was originally. I think that matches the original design intention or at the very least it lets users catch haywire key truncation. Thirdly, it moves the changelog entry to the top of the file, where new entries go. I couldn't understand what the entry was saying so I tried to rewrite it.
Diffstat (limited to 'activerecord/test/cases/arel/nodes')
0 files changed, 0 insertions, 0 deletions