django-zen-queries VS django-cacheops

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

Here is an example of such thing https://github.com/Suor/django-cacheops/blob/8b3a79de29b2545...

django-cacheops is a great package https://github.com/Suor/django-cacheops

Nuts, I was hoping that this was an evolution of https://github.com/Suor/django-cacheops which uses Redis to cache and invalidate ORM result sets by an abstracted representation of filter values. It works, but has a lot of magic (as is the Django way) and takes some tending-to in production.

i came across this and this i am failing to understand what is the difference between the two and which is better.

The solution I recommend is setting up the caching backend using like redis then bringing in this awesome project django-cacheops! Takes 5 minutes to set up (literally) and you’re done!

We use django cacheops with redis and its incredible!