Changes between Version 2 and Version 3 of Ticket #33882, comment 18


Ignore:
Timestamp:
Sep 3, 2024, 4:07:23 PM (3 months ago)
Author:
André S. Hansen

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33882, comment 18

    v2 v3  
    1 I am hesitant going for async django until transaction support is added or a cleaner solution than having to use **sync_to_async** is available. The problem with this workaround is that it forces you to write all code inside the transaction sync. Which is going to be a mess when transaction and non-transaction scopes want to use the same code/logic.
     1I am hesitant going for async django until transaction support is added or a cleaner solution than having to use **sync_to_async** is available. The problem with this workaround is that it forces you to write all code inside the transaction as sync. Which is going to be a mess when transaction and non-transaction scopes want to use the same code/logic.
    22
    3 Imagine the following simple example that illustrate the mess one will get in.
     3The following example illustrate the problem
    44
    55{{{
Back to Top