Playlist link: kzfaq.info/get/bejne/e9lypKyL0riWhZc.html

You are the best thing that has ever happened to Django. Thank you. The best thing we can do, is buy you coffee. You deserve it.

I've watched so many Django videos and you're the first person I've come across that talks about this. Great work once again!

Thanks, You have taken Django to another level❤

love your cool advanced content... you are my django master. thank you for sharing ❤

Thanks, You have taken me to another level in django

excellent, thanks again! been watching your videos for a while now.. very well explained!

Your channel is peace of gold on youtube. Exact hit that I'd been searching for

Great content, easy concise and well paced. You are a real masterclass educator.

Thanks alot, was wondering why my application was so slow and this completely fixed it. Love this channel!

Thank you so much for this great channel 🥰🥰

I have used prefetch and select related blindly in real time project (Not knowing in-depth) and query time was reduced. But this explanation is too good and I got to know the real use. Thank you so much man.

You are true genius❤

Nice video! Very helpful.

Dude i love ur stuff. For me the special highlight tho is every time you say boolean I hear boullion

Thanks

Awesome as always 🥳🎉

awesome

thanks

Very important video.

Thank you

Love the content

I hope your channel be 1m subs ❤

Excellent video!! Thank you!

Thank you!

Sure it is very good

Amazing

Thank you, sir

Nice, Thanks!

Great!

Awesome!

thank

awesome video❤... could you also post a video on caching in django

Great tutorial! but can you let me know, why we are configuring django to server static files explicitly, when its already being done by runserver implicitly?

Instead of using the 'ratings' related_name and then filtering the queryset, could you have created another Prefetch object for that like you did with monthly sales and call it five_star_ratings or something?

nice video ! Do you have any suggestions for debugging the queries with django rest framework ?

Is debugtoolbar still usable for rest APIs?

Is it mandatory for me to work on templates for each endpoints if i wish to use the django debug toolbar?

I have updated date of sale of a restaurant to two months before. But still I'm getting the sale object

What about ur Django-leaflet series?

Is the management/command pretty much the same as the scripts in the extensions just best practice to put code to import data as a command rather than a script? Also, I think there may be an error with the Prefetch() code because if I change "month_ago" to "two_days_ago": two_days_ago = timezone.now() - timezone.timedelta(days=2) and print: Sale.objects.filter(datetime__gte=two_days_ago) I get a queryset with 2 objects but when I print the below I get a queryset of 6 Restaurant.objects.prefetch_related('ratings', two_days_ago).filter(ratings__rating=5) and when I print the totals it's exactly the same as when we get all of the Sales rather than the Sales for a specific date. It's a list with 4 results. Hope this makes sense and not an issue of how I coded along.

what if im using django rest framework and im working on api ?

N+1 has been kicking my @ss

hello sir, thanks for the explanation, i just wanted to know when will the select_related not working, I'm using a different ways to implement it here: ` loans = self.lending_loans.select_related('lender').filter(lender_loan_status__in=[Loan.STATUS.funded, Loan.STATUS.completed]) ` Where lending_loans is the related name of the the FK inside the loan model.

Great video! restaurants = Restaurant.objects.prefetch_related('rating_set', monthly_sales).filter(rating__rating=5) restaurants.annotate(total=Sum('sale__income')) I'm cross referencing the values printed out on the terminal vs the dB Browser table. The Sum value doubles up for Restaurant rows when the query set returns the same restaurant name twice (i.e. Bombay Bustle has 2-off 5-star entries, and it's sales are summed x2 - instead of the x1 which is expected). I tried troubleshooting with ChatGPT using the distinct() function on the filtered query set. It worked on the query set, but did not translate with the annotate function. Just wondering if anyone else encountered the same anomaly?