From b2b02e7c05729aaeec9afe4896bf27aa02e815d1 Mon Sep 17 00:00:00 2001
From: austinried <4966622+austinried@users.noreply.github.com>
Date: Fri, 9 Oct 2026 05:12:41 +0000
Subject: [PATCH] logging: log upsert conflicts at verbose

Room's @Upsert insert-then-update fires a uniqueness conflict on every existing-row write (e.g. each playback-cursor save), which is normal control flow and flooded the debug file at debug level. Move it below the file threshold so the shared log stays quiet.
---
 app/src/main/kotlin/com/subtracks/log/Log.kt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/src/main/kotlin/com/subtracks/log/Log.kt b/app/src/main/kotlin/com/subtracks/log/Log.kt
index 38c14f83..e580c779 100644
--- a/app/src/main/kotlin/com/subtracks/log/Log.kt
+++ b/app/src/main/kotlin/com/subtracks/log/Log.kt
@@ -109,7 +109,7 @@ object Log {
         val failure = execution.error
         if (failure != null) {
             if (isUpsertConflict(execution.sql, failure)) {
-                d("sql", "upsert fallback conflict: ${shortSql(execution.sql)}")
+                v("sql", "upsert fallback conflict: ${shortSql(execution.sql)}")
             } else {
                 e("sql", "failed: ${shortSql(execution.sql)}", failure)
             }