5-2-stable: Fix touch option to behave consistently with Persistence#touch method
#33148
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…thod `touch` option was added to `increment!` (rails#27660) and `update_counters` (rails#26995). But that option behaves inconsistently with `Persistence#touch` method. If `touch` option is passed attribute names, it won't update update_at/on attributes unlike `Persistence#touch` method. Due to changed from `Persistence#touch` to `increment!` with `touch` option, rails#31405 has a regression that `counter_cache` with `touch` option which is passed attribute names won't update update_at/on attributes. I think that the inconsistency is not intended. To get back consistency, ensure that `touch` option updates update_at/on attributes.
|
|
rafaelfranca
pushed a commit
that referenced
this pull request
Oct 25, 2018
5-2-stable: Fix `touch` option to behave consistently with `Persistence#touch` method
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of #33107.
touchoption was added toincrement!(#27660) andupdate_counters(#26995). But that option behaves inconsistently with
Persistence#touchmethod.If
touchoption is passed attribute names, it won't updateupdate_at/on attributes unlike
Persistence#touchmethod.Due to changed from
Persistence#touchtoincrement!withtouchoption, #31405 has a regression that
counter_cachewithtouchoptionwhich is passed attribute names won't update update_at/on attributes.
I think that the inconsistency is not intended. To get back consistency,
ensure that
touchoption updates update_at/on attributes.