diff options
| author | Ryuta Kamizono <kamipo@gmail.com> | 2017-07-21 12:26:09 +0900 |
|---|---|---|
| committer | Ryuta Kamizono <kamipo@gmail.com> | 2019-01-18 16:01:14 +0900 |
| commit | c196ca72a0dfbea5f1730f830ea20a9e02a3c737 (patch) | |
| tree | 2017197758672519af2a2ef44eb674af35491a99 /activesupport/test/testing/constant_lookup_test.rb | |
| parent | 31ffbf8d5056137717da3f11d28c4fbd7fbc8f07 (diff) | |
| download | rails-c196ca72a0dfbea5f1730f830ea20a9e02a3c737.tar.gz rails-c196ca72a0dfbea5f1730f830ea20a9e02a3c737.tar.bz2 rails-c196ca72a0dfbea5f1730f830ea20a9e02a3c737.zip | |
Ensure `StatementCache#execute` never raises `RangeError`
Since 31ffbf8d, finder methods no longer raise `RangeError`. So
`StatementCache#execute` is the only place to raise the exception for
finder queries.
`StatementCache` is used for simple equality queries in the codebase.
This means that if `StatementCache#execute` raises `RangeError`, the
result could always be regarded as empty.
So `StatementCache#execute` just return nil in that range error case,
and treat that as empty in the caller side, then we can avoid catching
the exception in much places.
Diffstat (limited to 'activesupport/test/testing/constant_lookup_test.rb')
0 files changed, 0 insertions, 0 deletions