-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
OpenBridge Sprint 216
When we use to trigger Work immediately, when scheduled, we kept the database related code inside a separate doXXX(..) transactional method. However now we've removed the code triggering Work we no longer need to the split.
When I was looking at it I thought it best to ensure:-
- ALL related database operations are in the same transaction for each operation
- The transactional methods are as short as possible
I therefore kept two methods.
- relates to
-
MGDOBR-436 Workers: Interleaved execution for same work
- Closed