Use correct integer value for forgotten (fix Postgres)

element-hq · Oct 15, 2024 · 9fda8d0 · 9fda8d0
1 parent 9d2586b
commit 9fda8d0
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/synapse/storage/databases/main/events.py b/synapse/storage/databases/main/events.py
@@ -1889,7 +1889,7 @@ def _update_current_state_txn(
                         membership_info.membership,
                         # Since this is a new membership, it isn't forgotten anymore (which
                         # matches how Synapse currently thinks about the forgotten status)
-                        False,
+                        0,
                         # XXX: We do not use `membership_info.membership_event_stream_ordering` here
                         # because it is an unreliable value. See XXX note above.
                         membership_info.membership_event_id,
@@ -2907,7 +2907,7 @@ def _store_room_members_txn(
                     "membership": event.membership,
                     # Since this is a new membership, it isn't forgotten anymore (which
                     # matches how Synapse currently thinks about the forgotten status)
-                    "forgotten": False,
+                    "forgotten": 0,
                     "event_stream_ordering": event.internal_metadata.stream_ordering,
                     "event_instance_name": event.internal_metadata.instance_name,
                 }