Models¶
CommandExecution
¶
CommandOutputPart
¶
Bases: Model
One sealed chunk of command output (at most PART_SIZE characters).
Output is stored as an ordered sequence of immutable parts per
(execution, field). Live flushes append at the database level to the
single active (highest-seq) part; when a part would exceed
PART_SIZE it is sealed and a new empty part becomes active.
RegisteredCommand
¶
Bases: Model
ScheduledCommand
¶
Bases: Model
Library-owned schedule definition — the source of truth.
Rows are materialized into the active runner's native schedule objects
(e.g. django-q2 Schedule) via the runner's schedule CRUD API; the
native reference is stored in backend_schedule_key. enabled=False
removes the native object but keeps this row (audit trail / re-enabling).