From e05e5c0e34b26509cdd27cd062362d73d85125e7 Mon Sep 17 00:00:00 2001
From: Gdub <290704+gwmullin@users.noreply.github.com>
Date: Tue, 1 Sep 2026 11:19:26 -0700
Subject: [PATCH] Change testcase to clarify that it covers the peewee behavior
 of on_conflict_ignore

---
 frigate/test/http_api/test_http_review.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/frigate/test/http_api/test_http_review.py b/frigate/test/http_api/test_http_review.py
index f6d5f2c661..9b97579a77 100644
--- a/frigate/test/http_api/test_http_review.py
+++ b/frigate/test/http_api/test_http_review.py
@@ -497,8 +497,8 @@ class TestHttpReview(BaseTestHttp):
             )
             assert user_review.has_been_reviewed == True
 
-    def test_post_reviews_viewed_concurrent_duplicate_does_not_raise(self):
-        """Regression: concurrent requests marking the same review must not 500.
+    def test_reviews_concurrent_insert_peewee_ignore(self):
+        """Validates that on_conflict_ignore() silently skips a duplicate insert
 
         Two requests can both SELECT and find no existing status, then both try
         to INSERT, hitting the unique (user_id, review_segment) constraint.