Richard van der Hoff 75fb10ee45 Clean up schema for event_edges (#12893) ... * Remove redundant references to `event_edges.room_id` We don't need to care about the room_id here, because we are already checking the event id. * Clean up the event_edges table We make a number of changes to `event_edges`: * We give the `room_id` and `is_state` columns defaults (null and false respectively) so that we can stop populating them. * We drop any rows that have `is_state` set true - they should no longer exist. * We drop any rows that do not exist in `events` - these should not exist either. * We drop the old unique constraint on all the colums, which wasn't much use. * We create a new unique index on `(event_id, prev_event_id)`. * We add a foreign key constraint to `events`. These happen rather differently depending on whether we are on Postgres or SQLite. For SQLite, we just rebuild the whole table, copying only the rows we want to keep. For Postgres, we try to do things in the background as much as possible. * Stop populating `event_edges.room_id` and `is_state` We can just rely on the defaults.		2022-06-15 12:29:42 +01:00
..
main	Clean up schema for event_edges (#12893)	2022-06-15 12:29:42 +01:00
state	Add a unique index to state_group_edges to prevent duplicates being accidentally introduced and the consequential impact to performance. (#12687)	2022-05-19 14:16:49 +01:00
__init__.py	Ensure that get_datastores().main is typed (#12070)	2022-02-25 10:20:40 +00:00