Skip to content

Remove emergency alerts database tables#4536

Merged
klssmith merged 1 commit into
mainfrom
ks-remove-emergency-alerts-schema-step-1
Aug 8, 2025
Merged

Remove emergency alerts database tables#4536
klssmith merged 1 commit into
mainfrom
ks-remove-emergency-alerts-schema-step-1

Conversation

@klssmith

@klssmith klssmith commented Aug 7, 2025

Copy link
Copy Markdown
Contributor

Now that there's no data that depends on these, we can delete the tables completely. This was important to do as separate steps, or we could end up in a case where have have fragments of broadcast services sitting in our database but without the broadcast-specific tables, which would leave us unsure as to what those services were.

This commit is taken from #4202. The earlier work in that PR has already been merged, and this is the first stage of removing the database schema, which I'm splitting into separate PRs instead of doing in one.

now that there's no data that depends on these, we can delete the
tables completely. this was important to do as separate steps, or we
could end up in a case where have have fragments of broadcast services
sitting in our database but without the broadcast-specific tables, which
would leave us unsure as to what those services were.
@klssmith

klssmith commented Aug 7, 2025

Copy link
Copy Markdown
Contributor Author

Every Squawk warning is "note: Dropping a table / column may break existing clients."

Comment thread migrations/versions/0510_delete_broadcast_tables.py
@klssmith klssmith merged commit 31fcf69 into main Aug 8, 2025
5 of 6 checks passed
@klssmith klssmith deleted the ks-remove-emergency-alerts-schema-step-1 branch August 8, 2025 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants