11 ms·
As an experienced Django developer, I found django-zen-queries very good for hygiene, and I'm going to start using it. I should also pay attention to django-deb
by stavros 5y ago
As an experienced Django developer, I found django-zen-queries very good for hygiene, and I'm going to start using it. I should also pay attention to django-debug-toolbar's query view more often.
I generally don't need to optimize my queries because my apps are small, but I should do that by default, because otherwise it's wasteful and it's not hard to do. It's just that Django's default doesn't encourage you too, but hopefully with Zen Queries it will.
- jmconfuzeus 5y agoMany developers never look at the SQL panel in debug toolbar. That's why I'm advocating to evaluate QuerySets before presenting any data. It's just a way to make less mistakes.
- stavros 5y agoYeah, completely agreed. That's why I like Zen Queries.
- Nextgrid 5y ago> I generally don't need to optimize my queries because my apps are small Same situation here. I find that being mindful of the ORM is enough to save me from obviously bad queries (fetching 100 objects and then running additional queries for each one), for the rest I get away with it as it's not a problem in practice. Sure, I will probably save an extra milisecond here and there and maybe in the end be able to run my entire DB off a very small computer, but (bare-metal) hardware is so cheap that a few stray queries here and there won't break the bank. Nevertheless I've installed the package and will be trying it out, but I have yet to be convinced that eliminating additional queries all the time is worth the extra developer effort.
- stavros 5y agoI tried it, and came to the same conclusion as you. Fortunately, the package doesn't require you to do it all the time, you can pick a few at-risk functions and only disallow template queries there.