mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-16 22:59:04 +02:00
94f9dcaa77
`161_attachment_task_id` and `162_attachment_task_id_index` (from #5164) merged after prefixes 161/162/163 were already taken on main by #5277, #5279, and #5296, leaving two migrations on each of 161 and 162. That trips TestMigrationNumericPrefixesStayUniqueAfterLegacySet, so the backend job now fails on every open PR. Renumber to the next free prefixes (164/165); the file contents are unchanged. Note for already-migrated databases: any DB that applied 161/162 has those versions recorded in schema_migrations. After this rename, reconcile the ledger (rename the recorded versions to 164/165) or reset the dev DB — otherwise the migrator re-runs the renamed files and the ADD COLUMN fails because the column already exists. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3 lines
56 B
SQL
3 lines
56 B
SQL
ALTER TABLE attachment
|
|
DROP COLUMN IF EXISTS task_id;
|