fix: assign supported_protocols when migration user db (#2126)

wireapp · Oct 13, 2023 · 1568bd6 · 1568bd6
1 parent be4f27b
commit 1568bd6
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/persistence/src/commonMain/db_user/com/wire/kalium/persistence/Users.sq b/persistence/src/commonMain/db_user/com/wire/kalium/persistence/Users.sq
@@ -27,7 +27,7 @@ CREATE TABLE User (
     incomplete_metadata INTEGER AS Boolean NOT NULL DEFAULT 0,
     expires_at INTEGER AS Instant,
     defederated INTEGER AS Boolean NOT NULL DEFAULT 0,
-    supported_protocols TEXT AS Set<SupportedProtocolEntity>,
+    supported_protocols TEXT AS Set<SupportedProtocolEntity> DEFAULT 'PROTEUS',
     active_one_on_one_conversation_id TEXT AS QualifiedIDEntity
 );
 CREATE INDEX user_team_index ON User(team);

diff --git a/persistence/src/commonMain/db_user/migrations/60.sqm b/persistence/src/commonMain/db_user/migrations/60.sqm
@@ -1,4 +1,4 @@
-ALTER TABLE User ADD COLUMN supported_protocols TEXT AS Set<SupportedProtocolEntity>;
+ALTER TABLE User ADD COLUMN supported_protocols TEXT AS Set<SupportedProtocolEntity> DEFAULT 'PROTEUS';
 
 DROP VIEW IF EXISTS ConversationDetails;