fix: declare the musehub#184 UNIQUE constraint in the ORM model too
Migration 0076 added a real DB-level UNIQUE constraint on musehub_issues(repo_id, number), but I forgot to also declare it in MusehubIssue.__table_args__ — caught immediately by the staging deploy's schema-drift gate (assert_schema_matches_orm), which correctly refused to proceed rather than let the ORM's view of the schema silently diverge from reality. Added UniqueConstraint("repo_id", "number", name="uq_musehub_issues_repo_id_number") matching the migration's constraint name exactly. tests/test_schema_parity.py and tests/test_schema_check.py (24 tests) pass; tests/test_musehub_issues.py (33 tests, including the new concurrency regression test) still pass.
sha256:6af09266d99c51a851b1b5fe426c8217022e79492cf023e120a53681733b1458
sha
~1
symbols
1 changed · 1072 in snapshot
files
sha256:645cc4768da5189e034d5715d02aa7d0b166673a45f0bd18a22d97bf721b78db
snapshot
~1
symbol modified
1
file changed
1072
files in snapshot
0
dead code introduced
Semantic Changes
1 symbol
Files Changed
~1
1072 in snapshot
~1
1072 in snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:6af09266d99c51a851b1b5fe426c8217022e79492cf023e120a53681733b1458 --body "your comment"
No comments yet. Be the first to start the discussion.