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.
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.
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!
