I've noticed that by default most people simply use the .save() method when updating single fields rather than specifying specific fields such as restaurant.save(update_fields=['name']). Is there much performance improvement specifying specific fields or should we stick to .save() for ease?
I think that update_fields can help if you have a lot of database overhead, as it does cut down the data that's being sent to the DB server. But for most apps, it won't really have much impact I don't think. save() should work fine! Might be interesting to do a video on load testing with these two (and other) techniques to try and quantify the performance difference. Might look into that!
Thanks so much man. Had an interesting observation in my SQL - My .save(update_fields=...) executed 50% SLOWER than my regular .save( ) ! Is this expected or is something wrong with my sqllite? Intuitively, I thought the opposite would happen.
Thank you alot sir , please make a playist about dajngo signals and continue with django rest framework , You are the best !
@@MuhammedKamaal thanks a lot! I’ll do the signals video soon!
Love this waited a month for this series 😅 Yes want to learn about signals.
Thanks 🙏 I’ll start preparing a signals video soon!
Saved! Gonna watch this during the weekend when I have more time. Thanks!
Thank you - enjoy the weekend :)
Yes, teach about Signals on Django. your work is really great and helpful. Keep it up!
Thanks for continuing this series.
Thanks for watching!
Much obliged!! You explain everything in such simple detail and it's been VERY helpful!! THANK you!!
Thanks a lot!
I'm grateful, man; you are the best.
Thanks a lot man - appreciate the comment, cheers!
Excellent series! Signals would be so helpful! Great channel :)
Thanks a lot! And noted, I will get round to a signals video soon!
Cool video as always.On top of that can you add functionality where you check multiple checkboxes and update with htmx and Django querysrt.
Thanks!
I'm doing an upcoming Django + HTMX series (building a finance tracker) - this exact functionality will be in this app, coming soon!
Thank you so much for this amazing playlist 🎉😊
No problem, glad you liked it, and thanks for the comment!
Thank you, All the best 😊
Playlist link: th-cam.com/video/EsBqIZmR2Uc/w-d-xo.html
Thanks again for this series, very helpful
Thank you, glad you are finding it helpful!
Great lesson
Thanks Justin!
YES to signals! 🤘
Got it! Will make one very soon.
+1 on signals
Will look into it! Thanks
MUCH OBLIGED and YESSSSSSSSSSS for signals
Thanks - will be doing this in the very near future (finally!)
I let you know I'm interested in you making a video about signals 😁
Thanks, will be doing something very soon!
I've noticed that by default most people simply use the .save() method when updating single fields rather than specifying specific fields such as restaurant.save(update_fields=['name']). Is there much performance improvement specifying specific fields or should we stick to .save() for ease?
I think that update_fields can help if you have a lot of database overhead, as it does cut down the data that's being sent to the DB server. But for most apps, it won't really have much impact I don't think. save() should work fine!
Might be interesting to do a video on load testing with these two (and other) techniques to try and quantify the performance difference. Might look into that!
Thanks so much man. Had an interesting observation in my SQL - My .save(update_fields=...) executed 50% SLOWER than my regular .save( ) ! Is this expected or is something wrong with my sqllite? Intuitively, I thought the opposite would happen.
That's interesting. No idea why that happens with SQLite. I agree, I'd have expected the opposite!
than kyou
You're welcome!
Please teach signals
Will do! Coming up soon...
Promo'SM