From 0b20e16e1f85aa9831863374c0148ff818327712 Mon Sep 17 00:00:00 2001 From: NguyenND Date: Tue, 4 Aug 2026 13:41:12 -0400 Subject: [PATCH] Aug 4 - Update code to follow up - MT12b (1) --- .../versions/phase48_schedule_parent_inspection.py | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/migrations/versions/phase48_schedule_parent_inspection.py b/migrations/versions/phase48_schedule_parent_inspection.py index 5578de6..856e576 100644 --- a/migrations/versions/phase48_schedule_parent_inspection.py +++ b/migrations/versions/phase48_schedule_parent_inspection.py @@ -27,9 +27,17 @@ with the same rule, so neither side of the pair can delete the other's history. Uses INFORMATION_SCHEMA existence checks — safe to re-run on every tenant DB. Additive only: nothing is renamed, retyped or dropped. + +Revision id note +---------------- +`alembic_version.version_num` is VARCHAR(32). The descriptive form +'phase48_schedule_parent_inspection' is 34 characters and fails the stamp UPDATE +after the DDL has already run. The id is abbreviated to fit, matching the +single-tenant chain's own 'phase45_sched_parent_insp'. The FILENAME stays +descriptive — Alembic keys on the `revision` string, not the filename. """ -revision = 'phase48_schedule_parent_inspection' +revision = 'phase48_sched_parent_insp' down_revision = 'phase47_schedule_end_date' branch_labels = None depends_on = None