Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Commit

Permalink
In light of #8255, use BIGINTs for destination_rooms
Browse files Browse the repository at this point in the history
  • Loading branch information
reivilibre committed Sep 4, 2020
1 parent 58f61f1 commit a4375d3
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
1 change: 1 addition & 0 deletions changelog.d/8256.misc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Track the latest event for every destination and room for catch-up after federation outage.
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit a4375d3

Please sign in to comment.