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

Stop populating events.content #3614

Merged
merged 3 commits into from
Jul 26, 2018
Merged

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Jul 26, 2018

This field is no longer read from, so we should stop populating it. Once we're
happy that this doesn't break everything, and a rollback is unlikely, we can
think about dropping the column.

This field is no longer read from, so we should stop populating it. Once we're
happy that this doesn't break everything, and a rollback is unlikely, we can
think about dropping the column.
There's no real point in ever making the column non-nullable, and doing so
breaks the sytests.
@richvdh richvdh requested a review from a team July 26, 2018 13:56
@turt2live
Copy link
Member

Are the event contents read elsewhere? Surely this is read from by federation somewhere, although maybe not explicitly?

@richvdh
Copy link
Member Author

richvdh commented Jul 26, 2018

hope not. #3060 saw to that

Copy link
Member

@erikjohnston erikjohnston left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm really quite scared about rewriting the SQLite schema without forcing a backup of the DB, but I don't really kbow what else to suggest other tbh

@richvdh richvdh merged commit 65c8dee into develop Jul 26, 2018
@richvdh richvdh deleted the rav/stop_populating_event_content branch August 2, 2018 11:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants