fix old migration to avoid unique constraints problems, closes #3447

zadam · Dec 22, 2022 · e05e4be · e05e4be
1 parent 5a3882f
commit e05e4be
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 15 deletions.
diff --git a/db/migrations/0192__add_memberId_to_entity_changes.sql b/db/migrations/0192__add_memberId_to_entity_changes.sql
@@ -1,4 +1,7 @@
-CREATE TABLE IF NOT EXISTS "mig_entity_changes" (
+DROP TABLE entity_changes;
+-- not preserving the data because of https://github.com/zadam/trilium/issues/3447
+
+CREATE TABLE IF NOT EXISTS "entity_changes" (
                                                     `id`	INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
                                                     `entityName`	TEXT NOT NULL,
                                                     `entityId`	TEXT NOT NULL,
@@ -11,13 +14,6 @@ CREATE TABLE IF NOT EXISTS "mig_entity_changes" (
                                                     `utcDateChanged` TEXT NOT NULL
 );
 
-INSERT INTO mig_entity_changes (id, entityName, entityId, hash, isErased, changeId, componentId, instanceId, isSynced, utcDateChanged)
-SELECT id, entityName, entityId, hash, isErased, changeId, '', '', isSynced, utcDateChanged FROM entity_changes;
-
-DROP TABLE  entity_changes;
-
-ALTER TABLE mig_entity_changes RENAME TO entity_changes;
-
 CREATE UNIQUE INDEX `IDX_entityChanges_entityName_entityId` ON "entity_changes" (
                                                                                  `entityName`,
                                                                                  `entityId`

diff --git a/package-lock.json b/package-lock.json