Matsalar N+1 query ita ce matsala mafi yawa ta Django ORM performance: samun alaƙa da abubuwan da ke maimaita a cikin loop yana bugi separate database query ga kowannensu. select_related da prefetch_related suna warware ta hanyar karɓar alaƙa data cikin inganci — suna abubuwan atunci masu mahimmanci.
books = Book.objects.()
book books:
(book.author.name)
Kowa book.author access yana bugin database sau ɗaya in jiya. Tare da littattafai 100, haka kuwa 101 queries — matsala muni, sneaky performance killer wanda yawanci ya nuni kawai a ƙarƙashin bayanan jiya-jiya.
# ✅ ONE query with a JOIN
books = Book.objects.select_related("author").all()
for book in books:
print(book.author.name) # NO extra queries — author was JOINed in
# 100 books → 1 query total
select_related yana gudnar da SQL JOIN domin karɓar abin alaƙa a kwankwaso query. Yi amfani da shi domin forward ForeignKey da OneToOne alaƙa (gida ɗaya abin alaƙa), inda JOIN ya zama efficient.
# ✅ TWO queries total (not N+1)
authors = Author.objects.prefetch_related("books").all()
for author in authors:
for book in author.books.all(): # NO extra queries — books were prefetched
print(book.title)
# query 1: all authors; query 2: all their books → Django joins them in Python
prefetch_related yana aiwatar da separate query domin abubuwan alaƙa kuma tana haɗi su a Python. Yi amfani da shi domin ManyToMany da reverse ForeignKey alaƙa (abubuwan da yawa alaƙa), inda JOIN zai ninka layuka cikin rashin inganci.
select_related → ForeignKey, OneToOne (forward, single object) → SQL JOIN, 1 query
prefetch_related → ManyToMany, reverse ForeignKey (many objects) → 2 queries, joined in Python
You can combine and chain them, and span relationships:
Book.objects.select_related("author").prefetch_related("tags")
Book.objects.select_related("author__publisher") # multi-level
✓ Django Debug Toolbar — shows the query count per page (spot N+1 visually)
✓ django-silk, or logging queries (connection.queries) to count them
→ If a page runs hundreds of similar queries, you likely have an N+1.
Matsalar N+1 query ita ce matakin mafi yawa da tesiri performance matsala a cikin Django aikace-aikace, kuma fahimtar select_related/prefetch_related ya zama mahimmanci domin rubuta code mai inganci.
Matsalar ta zama insidious saboda jami'in kaidai da aka saba (na ORM syntax da ke buɓuzawa saman sanin abubuwan alaƙa book.author.name) ta hankali yana bugi database query kowa lokaci — code wanda ke aiki sosai da raɗiyoyin kaɗan yana raguwa cikin rashin inganci tare da bayanan jiya (raɗiyoyin 100 → 101 queries), yawanci an gano kawai a production a ƙarƙashin nauyi.
Wadata guda biyu sune standard, mahimmanci mafita: select_related tana amfani da SQL JOIN domin karɓar forward ForeignKey/OneToOne alaƙa a single query, yayin da prefetch_related tana amfani da separate query (haɗiya a Python) domin ManyToMany/reverse-ForeignKey alaƙa inda JOIN zai kasance rashin inganci — kuma sanin menene ne a yi amfani domin menene alaƙa shi ne maɓalli mahimmanci.
Kunna su yana juyawa raɓuɓɓu mara jiya queries zuwa ɗaya ko biyu, yawanci yana inganta performance na shafi cikin girma.
Warwar optimization nan ta zama mahimmanci da ya yi kusan a ainon cewa gani matsalar N+1 (amfani da kayan aiki kamar Django Debug Toolbar domin gano kasanci da yawa na query) da amfani daidai shine mahimmanci ɗin kakakin persone, daidai saboda yana nuna ainihi, performance-critical ORM fahimta kuma bambance ma'aniyoyu waɗanda suke rubuta Django code mai inganci daga waɗanda aikace-aikace nsu suna juyawa zuwa cikin rashin inganci yayin da bayani ya girma.
Shakamau kuwa daga cikin suna bugun aiki a cikin Django tambaya jiya, daidai saboda yana nuna ainihi, performance-critical ORM fahimta.