From 2ed910459f47d52cbc14adf8c75c63d67b298c6e Mon Sep 17 00:00:00 2001 From: Bogdan Date: Thu, 1 Jan 2026 16:35:10 +0200 Subject: [PATCH] Avoid unique constraints for primary keys in SQLite migrations (cherry picked from commit c70de927a5113a3029478c539ca0f7f3095e07e9) --- .../Datastore/Migration/Framework/SqliteSchemaDumper.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/NzbDrone.Core/Datastore/Migration/Framework/SqliteSchemaDumper.cs b/src/NzbDrone.Core/Datastore/Migration/Framework/SqliteSchemaDumper.cs index a56384466..f11f735c1 100644 --- a/src/NzbDrone.Core/Datastore/Migration/Framework/SqliteSchemaDumper.cs +++ b/src/NzbDrone.Core/Datastore/Migration/Framework/SqliteSchemaDumper.cs @@ -120,7 +120,7 @@ protected virtual ColumnDefinition ParseColumnDefinition(SqliteSyntaxReader read column.IsPrimaryKey = upper.Contains("PRIMARY KEY"); column.IsIdentity = upper.Contains("AUTOINCREMENT"); column.IsNullable = !upper.Contains("NOT NULL") && !upper.Contains("PRIMARY KEY"); - column.IsUnique = upper.Contains("UNIQUE") || upper.Contains("PRIMARY KEY"); + column.IsUnique = upper.Contains("UNIQUE"); } return column;