this tutorial helped me a lot to understand django database transactions. The best thing is that he has explained the topic by referring to the django documentation.
Thanks for the video. Great content as always. Finally prompted me to sort some of my code out. Any plans to do anything on async or threading/Mutliprocessing in Django? very limited guidance and docs out there on this kind of stuff. Anyway, thantks again!
Wow, Amazing tutorial!!, I have a question if i have a function and this is called twice at the same time for refreshing the token of the user the first request when i trying to get the user it works successfully, the second API call for this function returning NoneType Object of the this user due to the refresh token was not equal to the refreshed token at the first, If i used the atomicity in this refresh_token view it will solve the problem or what should i do?
Thank you! I'm not sure, but I think when you get the NEW refresh token for the first API call - the original refresh token becomes invalid. If you then call the refresh endpoint AGAIN with that original refresh token (instead of the new one that was issued) - you'll probably get the error or the NoneType response. You need to always pass the most recently issued token from the client. I think this is more of a client-side issue than a Django/DB issue, but again - not 100% sure.
ORM Playlist link: ua-cam.com/video/EsBqIZmR2Uc/v-deo.html
This is by far, the most well explained video of Django Transactions. Thanks for your great video!
Thanks a lot Andres!
this tutorial helped me a lot to understand django database transactions. The best thing is that he has explained the topic by referring to the django documentation.
Nothing better than starting my week with a BugBytes video, great explanation of atomic transactions.
Thanks a lot Rob!
Thank you, for the great explanation. 🙏
Thanks a lot - glad it was helpful and thank you for watching!
Thank you so much mate, It can't be clearer than this. I will get into the habit of working with transaction now !
Thanks mate!
Finally I found how to manage num of items in stock without any risks
Thanks for the great video! Atomic transactions was one aspect of Django that I hadn't delved into before! Cheers!
Thanks a lot! Glad it was something new to learn!
Increíble, gracias 🫂🙌🏻
Thank you!
Very nice and deep example, thanks a lot!
Thank you!
Nice one .Very important video.
Thank you!
Great as always .
Thanks a lot!!
Nice one. Thanks for the gist.
Thanks for watching!
Bravo 👏👏👏👏👏👏👍👍👍
Thanks a lot!
thank you!
Thanks a lot!
Thanks for the video. Great content as always. Finally prompted me to sort some of my code out. Any plans to do anything on async or threading/Mutliprocessing in Django? very limited guidance and docs out there on this kind of stuff. Anyway, thantks again!
Thanks! It's an interesting topic but I've not really considered a video on this yet. I'll have a think about it though - cheers for the suggestion!
thank
Thanks for watching!
Hi, could you please share a tutorial for bulk update using atomic !!!
Can't we use lambdas in callbacks? I am not sure, but I genuinely thought that's what they are for
Hello, your videos are amazing, i am using htmx, but when i use hx-get in button, after this dont load js, how i can to fix this?
Wow, Amazing tutorial!!, I have a question if i have a function and this is called twice at the same time for refreshing the token of the user the first request when i trying to get the user it works successfully, the second API call for this function returning NoneType Object of the this user due to the refresh token was not equal to the refreshed token at the first,
If i used the atomicity in this refresh_token view it will solve the problem or what should i do?
Thank you!
I'm not sure, but I think when you get the NEW refresh token for the first API call - the original refresh token becomes invalid. If you then call the refresh endpoint AGAIN with that original refresh token (instead of the new one that was issued) - you'll probably get the error or the NoneType response. You need to always pass the most recently issued token from the client.
I think this is more of a client-side issue than a Django/DB issue, but again - not 100% sure.
@@bugbytes3923 thank you very much sir 💕💕
please i need the link to the codebase repo on Github