Removing a subscription also removes any associated events. This is a pretty bad situation, because we lose all of the information about previous events whenever somebody changes up their subscription.
Even more generally, are a bunch of mutations happening with subscriptions. We should figure out a good way to represent all previous subscriptions in the database and UI, so that we don't lose any vital information.
One way to handle this might be to introduce the concept of a "current" subscription. Each block would only have a single current subscription. All other subscriptions associated with the block would need to be deactivated. The current subscription could either be active or not-yet-activated.
Removing a subscription also removes any associated events. This is a pretty bad situation, because we lose all of the information about previous events whenever somebody changes up their subscription.
Even more generally, are a bunch of mutations happening with subscriptions. We should figure out a good way to represent all previous subscriptions in the database and UI, so that we don't lose any vital information.
One way to handle this might be to introduce the concept of a "current" subscription. Each block would only have a single current subscription. All other subscriptions associated with the block would need to be deactivated. The current subscription could either be active or not-yet-activated.