Details
-
Task
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
In AURORA-1386 it was necessary to relax the transaction isolation to match development patterns used with MemStorage. Now that we have a storage engine that allows for more strict transaction isolation, it would be nice to use them.
To support this, we need a pattern for queuing asynchronous work while performing a transaction, but only commence the work once the transaction has successfully been committed.
Attachments
Issue Links
- is related to
-
AURORA-1395 RescheduleCalculator precondition fails when using DbTaskStore
- Resolved