Let the Task State Machine run in a single database transaction #99408

Open
opened 2022-07-04 15:08:17 +02:00 by Sybren A. Stüvel · 2 comments

Currently each call to the persistence layer runs in its own database transaction. It would be nice if it had explicit transaction control, so that the Task State Machine can manage its own transaction boundaries.

Currently each call to the persistence layer runs in its own database transaction. It would be nice if it had explicit transaction control, so that the Task State Machine can manage its own transaction boundaries.
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Sybren A. Stüvel added
Type
To Do
and removed
Type
Report
labels 2023-02-17 11:17:02 +01:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#99408
No description provided.