diff options
author | Olivier Lacan <hi@olivierlacan.com> | 2016-10-19 00:59:21 +0200 |
---|---|---|
committer | Olivier Lacan <hi@olivierlacan.com> | 2017-12-13 20:13:21 -0500 |
commit | 3876defd7c951335129fa92c573c7b8fce085aac (patch) | |
tree | ac53702d700c0f66f1bc235749f7ce1847395cc7 /activesupport/test/core_ext/kernel | |
parent | 65e994c063fdc42265712854598649ec7607faec (diff) | |
download | rails-3876defd7c951335129fa92c573c7b8fce085aac.tar.gz rails-3876defd7c951335129fa92c573c7b8fce085aac.tar.bz2 rails-3876defd7c951335129fa92c573c7b8fce085aac.zip |
Log call site for all queries
This new ActiveRecord configuration option allows you to easily
pinpoint what line of application code is triggering SQL queries in the
development log by appending below each SQL statement log the line of
Ruby code that triggered it.
It’s useful with N+1 issues, and to locate stray queries.
By default this new option ignores Rails and Ruby code in order to
surface only callers from your application Ruby code or your gems.
It is enabled on newly generated Rails 5.2 applications and can be
enabled on existing Rails applications:
```ruby
Rails.application.configure do
# ...
config.active_record.verbose_query_logs = true
end
```
The `rails app:upgrade` task will also add it to
`config/development.rb`.
This feature purposely avoids coupling with
ActiveSupport::BacktraceCleaner since ActiveRecord can be used without
ActiveRecord. This decision can be reverted in the future to allow more
configurable backtraces (the exclusion of gem callers for example).
Diffstat (limited to 'activesupport/test/core_ext/kernel')
0 files changed, 0 insertions, 0 deletions