Files
notifications-api/migrations
Leo Hemsted 36ae5fadf6 add broadcast_event table
It's clear that we need a way to track updates to a broadcast message.
It's also clear that we'll need some kind of audit log that captures
exactly what was sent out in a message.

This commit adds a new database table, `broadcast_event`, which maps 1:1
with CAP XML sent to the CBCs. We'll create one of these just before
sending out.

The main driver for this was that cancel and update messages need to
contain a list of references of all previous messages that they're
amending. This is of format `{sender},{identifier},{sent_timestamp}`,
and the identifier itself needs to be unique for each message.
2020-07-28 12:10:18 +01:00
..
2020-07-28 12:10:18 +01:00

Generic single-database configuration.

flask db migrate to generate migration script.

flask db upgrade to upgrade db with script.

flask db downgrade to rollback db changes.

flask db current to show current script.