From 56c54c3fef27af6a4106c03bf8e7acd3ceb8b36d Mon Sep 17 00:00:00 2001 From: devs6186 Date: Thu, 19 Feb 2026 02:09:34 +0530 Subject: [PATCH] [db/models] Remove duplicate unique-prx constraint on pull_requests Fixes #3192 - The pull_requests table declared two identical UniqueConstraint entries on (repo_id, pr_src_id): "unique-pr" and "unique-prx" - ON CONFLICT (pr_url) in bulk_insert_dicts only catches conflicts on "pull-request-insert-unique"; conflicts on "unique-prx" bypass the upsert handler and surface as uncaught IntegrityErrors - Drop the redundant "unique-prx" declaration from the model - A companion Alembic migration is needed to DROP CONSTRAINT "unique-prx" on existing databases Signed-off-by: devs6186 --- augur/application/db/models/augur_data.py | 1 - 1 file changed, 1 deletion(-) diff --git a/augur/application/db/models/augur_data.py b/augur/application/db/models/augur_data.py index 78c2ce7151..53dffc49b1 100644 --- a/augur/application/db/models/augur_data.py +++ b/augur/application/db/models/augur_data.py @@ -1712,7 +1712,6 @@ class PullRequest(Base): __tablename__ = "pull_requests" __table_args__ = ( UniqueConstraint("repo_id", "pr_src_id", name="unique-pr"), - UniqueConstraint("repo_id", "pr_src_id", name="unique-prx"), UniqueConstraint("pr_url", name="pull-request-insert-unique"), Index("id_node", "pr_src_id", "pr_src_node_id"), Index(