Caching Defaults Not Configurable

[stephendolan]

Expected behavior vs actual behavior

I expected for AMS to allow a column other than updated_at to be used as a default for naming cache entries, but there is no such configuration option listed in the Cache README or Configuration README.

Steps to reproduce

1. Create a model without updated_at, instead calling the field something like modified_at.
2. Create an instance of the model, and verify that it was cached.
3. Update the instance you created, and verify that no new cache entry was set and no previous entry was expired.
4. Fetch the key from the cache, and verify that the values are still the old ones.

Environment

Rails 5.1.0
Redis 3.2.6
AMS 0.10.3
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin16]
Mac OSX Sierra 10.12.2

[bf4]

@stephendolan AMS caching requires a method named updated_at. Is there a reason you can't do something like alias_attribute :updated_at, :modified_at?

[bf4]

@stephendolan You can also write your own cache_key method in the serializer or your model... e.g. https://github.com/rails-api/active_model_serializers/blob/b709cd41e62574d8e1afcf43fe0c0eb277f80220/docs/general/serializers.md#cache_key

[stephendolan]

@bf4 Thank you, I think the second method is preferable to adding the alias_attribute to every model I have.

Do you mind if I open a pull request to add a link to that README section on the caching page as well? I must have missed that specific function when I was reading through the other documentation trying to find something that I could use.

[bf4]

Yes, please! :) B mobile phone

…

On Jan 6, 2017, at 9:41 AM, Stephen Dolan ***@***.***> wrote: @bf4 Thank you, I think the second method is preferable to adding the alias_attribute to every model I have. Do you mind if I open a pull request to add a link to that README section on the caching page as well? I must have missed that specific function when I was reading through the other documentation trying to find something that I could use. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.