test(db): strengthen the zone_name DROP COLUMN migration tests #261
Labels
No labels
blocked
bug
enhancement
high-priority
low-priority
needs-info
needs-triage
ready-for-agent
ready-for-human
referenced
research
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gabogg/hikcentral#261
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
P3 follow-up from PR #234 review pass 2 (both axes).
Finding
DROP COLUMNstatement (tests/test_camera_schema_migration.py:152), so nothing has changed yet when it fails. #209 says "If the copy fails partway, the original table and data survive". A reviewer's probe shows that a failure after the DROP (atidx_cycles_door_timeor the provenance UPDATE) rolls back correctly, but no test covers it.REAL_LEGACY_DDLisn't the real legacy definition (:12-29). It already hasis_excluded, aresource_group_codeFK and acamera_groupstable, so the suite never runs DROP followed by the ADD COLUMN migrations on the truece0ff5dschema.FailingConnection.executehas no user. No test sends its failure point throughconn.execute.Acceptance Criteria
ce0ff5dDDL, or rename the fixture to say what it is.