Django Database Transactions / atomic() function

Поділитися
Вставка
  • Опубліковано 26 жов 2024

КОМЕНТАРІ • 38

  • @bugbytes3923
    @bugbytes3923  6 місяців тому +1

    ORM Playlist link: ua-cam.com/video/EsBqIZmR2Uc/v-deo.html

  • @andresbenitez1299
    @andresbenitez1299 9 місяців тому +4

    This is by far, the most well explained video of Django Transactions. Thanks for your great video!

  • @muhammadtayyabtahirqureshi7186
    @muhammadtayyabtahirqureshi7186 3 місяці тому

    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.

  • @robhafemeister3100
    @robhafemeister3100 Рік тому +4

    Nothing better than starting my week with a BugBytes video, great explanation of atomic transactions.

  • @Khaled-fo7tr
    @Khaled-fo7tr 2 місяці тому +1

    Thank you, for the great explanation. 🙏

    • @bugbytes3923
      @bugbytes3923  2 місяці тому

      Thanks a lot - glad it was helpful and thank you for watching!

  • @seydinaoumarsamabaly1806
    @seydinaoumarsamabaly1806 Рік тому +1

    Thank you so much mate, It can't be clearer than this. I will get into the habit of working with transaction now !

  • @Yarkanlaki
    @Yarkanlaki 6 місяців тому

    Finally I found how to manage num of items in stock without any risks

  • @Dorso2009
    @Dorso2009 Рік тому

    Thanks for the great video! Atomic transactions was one aspect of Django that I hadn't delved into before! Cheers!

    • @bugbytes3923
      @bugbytes3923  Рік тому

      Thanks a lot! Glad it was something new to learn!

  • @qwee-c4r
    @qwee-c4r 3 місяці тому

    Increíble, gracias 🫂🙌🏻

  • @CristianMolina
    @CristianMolina 11 місяців тому

    Very nice and deep example, thanks a lot!

  • @repotranstech
    @repotranstech Рік тому +1

    Nice one .Very important video.

  • @wazidmalik6824
    @wazidmalik6824 Рік тому +1

    Great as always .

  • @AmoahDevLabs
    @AmoahDevLabs Рік тому +1

    Nice one. Thanks for the gist.

  • @mohanaryal5940
    @mohanaryal5940 23 дні тому +1

    Bravo 👏👏👏👏👏👏👍👍👍

  • @aashayamballi
    @aashayamballi Рік тому

    thank you!

  • @craigphollingsworth1460
    @craigphollingsworth1460 Рік тому

    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!

    • @bugbytes3923
      @bugbytes3923  Рік тому

      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!

  • @frameff9073
    @frameff9073 Рік тому +2

    thank

  • @rokibulhaque1673
    @rokibulhaque1673 11 місяців тому

    Hi, could you please share a tutorial for bulk update using atomic !!!

  • @firstandlast4435
    @firstandlast4435 5 місяців тому

    Can't we use lambdas in callbacks? I am not sure, but I genuinely thought that's what they are for

  • @leohenrique5038
    @leohenrique5038 Рік тому

    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?

  • @Ahmedesmail07
    @Ahmedesmail07 Рік тому

    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?

    • @bugbytes3923
      @bugbytes3923  Рік тому +1

      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.

    • @Ahmedesmail07
      @Ahmedesmail07 Рік тому

      @@bugbytes3923 thank you very much sir 💕💕

  • @ChristianForexTradersCommunity

    please i need the link to the codebase repo on Github