Taming the beast that is the Django ORM – An introduction

Re:Taming the beast that is the Django ORM – An introduction by oliwarner on Sunday September 01, 2024 @08:22AM (#41416383)

Not really.

.prefetch_related (for whole models) and annotate/Subquery (for fields or aggregates) have existed for many years, alongside a pile of aggregate functions which have existed forever and have improved.

Whether or not you use the tools given to you is a sign of developer quality and experience. You can easily avoid n+1 99% of the time but you have to appreciate the problem exists.

I think the Django project demanding some competence is okay.

[ Parent | on HN ]

Re:Taming the beast that is the Django ORM – An introduction by rowanseymour on Sunday September 01, 2024 @09:02AM (#41416678)

Not sure you understand my complaint because forcing the user to track down N+1 queries to know where they're missing .prefetch_related is the problem. I don't want to fix something 99% of the time. I want my ORM to enforce correctness 100% of the time.

[ Parent | on HN ]