diff options
| author | Samuel Cochran <sj26@sj26.com> | 2016-09-30 15:26:19 +1000 |
|---|---|---|
| committer | Matthew Draper <matthew@trebex.net> | 2016-10-26 15:42:23 -0500 |
| commit | fa7efca553e325b2aabb087a4eddf4560c356094 (patch) | |
| tree | 6397ac9dd2d763d62d33dbf1ca9244e1d74d958f /guides/source/active_record_querying.md | |
| parent | 3b50fb6b2f413b4bfe638b3c9839fe7db5077f73 (diff) | |
| download | rails-fa7efca553e325b2aabb087a4eddf4560c356094.tar.gz rails-fa7efca553e325b2aabb087a4eddf4560c356094.tar.bz2 rails-fa7efca553e325b2aabb087a4eddf4560c356094.zip | |
Clear the correct query cache
This executor currently relies on `ActiveRecord::Base.connection` not
changing between `prepare` and `complete`. If something else returns
the current ActiveRecord connection to the pool early then this
`complete` call will fail to clear the correct query cache and restore
the original `query_cache_enabled` status.
This has for example been happening in Sidekiq:
https://github.com/mperham/sidekiq/pull/3166
We can just keep track of the connection as part of the exector state.
Diffstat (limited to 'guides/source/active_record_querying.md')
0 files changed, 0 insertions, 0 deletions