diff options
| author | schneems <richard.schneeman+foo@gmail.com> | 2018-10-15 15:31:12 -0500 |
|---|---|---|
| committer | schneems <richard.schneeman+foo@gmail.com> | 2018-10-17 11:05:05 -0500 |
| commit | 2f99da00c7b311af0bc5969985eee97937790e4f (patch) | |
| tree | 971997f10298c1a6ea27d53dde9f1688d5a150f4 /activerecord/lib/arel/nodes/update_statement.rb | |
| parent | 04454839a1a07cacac58cdf756a6b8e3adde0ef5 (diff) | |
| download | rails-2f99da00c7b311af0bc5969985eee97937790e4f.tar.gz rails-2f99da00c7b311af0bc5969985eee97937790e4f.tar.bz2 rails-2f99da00c7b311af0bc5969985eee97937790e4f.zip | |
Do not silently fail to generate a cache_version
When an `updated_at` column exists on the model, but is not available on the instance (likely due to a select), we should raise an error rather than silently not generating a cache_version. Without this behavior it's likely that cache entries will not be able to be invalidated and this will happen without notice.
This behavior was reported and described by @lsylvester in https://github.com/rails/rails/pull/34197#issuecomment-429668759.
Diffstat (limited to 'activerecord/lib/arel/nodes/update_statement.rb')
0 files changed, 0 insertions, 0 deletions