You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(runs): deduplicate run tables against job_executions
Make the run primary key the job execution id: promote job_execution_id
to the primary key (also a foreign key to job_executions with cascade on
delete) and drop the duplicated status, end-time, log-message, and
process-id columns. Lifecycle status and timestamps are read through the
job_execution relationship; the run tables keep only their result and
progress data.
- Stop writing the duplicated columns in the profiling and test handlers
- Collapse dual-id lookups to a single id lookup (get_by_id_or_job -> get,
drop get_job_execution_ids); the run id is the job execution id
- Collapse the hand-rolled cascade delete to a single job_executions
delete now that the foreign-key chain cascades
- Migration 0193: rewrite external references to the job execution id,
promote the primary key, add the cascade foreign keys, drop the
duplicated columns
- Repoint score-rollup and entity-list SQL templates to job_executions
for run status
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments