From 7513006b09e0fdaa4660c21e32adb0dfa0603c1e Mon Sep 17 00:00:00 2001
From: reivilibre <38398653+reivilibre@users.noreply.github.com>
Date: Fri, 4 Sep 2020 15:07:29 +0100
Subject: In light of #8255, use BIGINTs for destination_rooms (#8256)

---
 .../databases/main/schema/delta/58/15_catchup_destination_rooms.sql     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'synapse/storage/databases/main')

diff --git a/synapse/storage/databases/main/schema/delta/58/15_catchup_destination_rooms.sql b/synapse/storage/databases/main/schema/delta/58/15_catchup_destination_rooms.sql
index 7f173f10d4..ebfbed7925 100644
--- a/synapse/storage/databases/main/schema/delta/58/15_catchup_destination_rooms.sql
+++ b/synapse/storage/databases/main/schema/delta/58/15_catchup_destination_rooms.sql
@@ -23,7 +23,7 @@ CREATE TABLE IF NOT EXISTS destination_rooms (
   -- the ID of the room in question
   room_id TEXT NOT NULL REFERENCES rooms (room_id),
   -- the stream_ordering of the event
-  stream_ordering INTEGER NOT NULL,
+  stream_ordering BIGINT NOT NULL,
   PRIMARY KEY (destination, room_id)
   -- We don't declare a foreign key on stream_ordering here because that'd mean
   -- we'd need to either maintain an index (expensive) or do a table scan of
-- 
cgit 1.4.1