We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We would like to use Prosopite for N+1 detections. For this, I configured Bullet in our project as follows:
config.after_initialize do ... Bullet.n_plus_one_query_enable = false Bullet.unused_eager_loading_enable = true Bullet.counter_cache_enable = true end
With these settings, Bullet tells me to remove includes:
AVOID eager loading detected Candidate => [:master_data, ...] Remove from your query: .includes([:master_data, ...])
But if I do so, Prosopite correctly find this N+1 problem:
SELECT "master_data".* FROM "master_data" WHERE "master_data"."candidate_id" = ? LIMIT 1 ...
And of course Bullet tells me correctly to add includes, when I change settings to Bullet.n_plus_one_query_enable = true:
Bullet.n_plus_one_query_enable = true
Candidate => [:master_data, ...] Add to your query: .includes([:master_data, ...])
It looks like the combination of
Bullet.n_plus_one_query_enable = false Bullet.unused_eager_loading_enable = true
does not work.
Our Rails environment:
Docker ruby:2.7.3-slim-buster rails 6.0.3.4 ruby 2.7.3p183 # Gemfile gem "puma", "~> 5.0" gem "pg", gem "bullet", "~> 6.1", ">= 6.1.4"
PS: maybe related to #481
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We would like to use Prosopite for N+1 detections. For this, I configured Bullet in our project as follows:
With these settings, Bullet tells me to remove includes:
But if I do so, Prosopite correctly find this N+1 problem:
And of course Bullet tells me correctly to add includes, when I change settings to
Bullet.n_plus_one_query_enable = true
:It looks like the combination of
does not work.
Our Rails environment:
PS: maybe related to #481
The text was updated successfully, but these errors were encountered: