From 2cd28131790cd65374484901f33d66ce0f6d4dcf Mon Sep 17 00:00:00 2001 From: Eric Eastwood Date: Mon, 12 Sep 2022 18:23:13 -0500 Subject: [PATCH] Grammar --- docs/development/database_schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development/database_schema.md b/docs/development/database_schema.md index 1d29ee5a8e..9648a939b7 100644 --- a/docs/development/database_schema.md +++ b/docs/development/database_schema.md @@ -210,7 +210,7 @@ scoped, we can reduce the possibility of a hash collision. When scoping (`PRIMARY KEY (room_id, event_id)`) and lookups should be done through the pair `(room_id, event_id)`. Another benefit of scoping `event_ids` to the room is that it makes it very easy to find and clean up everything in a room when it -needs to be purged (no need to sub-`select` query or join from the `events` +needs to be purged (no need to use sub-`select` query or join from the `events` table). `event_id` global uniqueness has had a lot debate in places like