django-zen-queries VS pellet

See also django-zen-queries https://github.com/dabapps/django-zen-queries , which can make it impossible for changes to a template to trigger queries.

I have no idea but the best way to make QuerySets explicit is by using a package called django-zen-queries.

> Making it more clear when you’re going to hit the database (explicit is better than implicit).

You might like https://github.com/dabapps/django-zen-queries

Gives you fine grain control about database queries

Simple middleware can warn you about lazy loading/N+1 queries. Most of the time people just forget it happens.

Try using: https://github.com/har777/pellet

Self plug: Checkout https://github.com/har777/pellet to easily find and fix django N+1 issues.

I usually add it to existing integration tests so that they raise exceptions on N+1. If test coverage is low then I would suggest sending the N+1 metrics to something like datadog. That way your users using the product will reveal all the N+1 issues on your monitoring solution.