mirror of
https://github.com/GSA/notifications-api.git
synced 2025-12-10 23:32:27 -05:00
A job only ever has one notification type. This is the first deploy, where the columns are added and populated. Next a data migration will happen to populate these new columns for the older jobs that do not have the values set. Then we stop populating the old columns and remove them. This refactoring of the table structure will make the queries to the table much easier to handle.
26 lines
729 B
Python
26 lines
729 B
Python
"""empty message
|
|
|
|
Revision ID: 0094_job_stats_update
|
|
Revises: 0093_data_gov_uk
|
|
Create Date: 2017-06-06 14:37:30.051647
|
|
|
|
"""
|
|
from alembic import op
|
|
import sqlalchemy as sa
|
|
|
|
# revision identifiers, used by Alembic.
|
|
revision = '0094_job_stats_update'
|
|
down_revision = '0093_data_gov_uk'
|
|
|
|
|
|
def upgrade():
|
|
op.add_column('job_statistics', sa.Column('sent', sa.BigInteger(), nullable=True))
|
|
op.add_column('job_statistics', sa.Column('delivered', sa.BigInteger(), nullable=True))
|
|
op.add_column('job_statistics', sa.Column('failed', sa.BigInteger(), nullable=True))
|
|
|
|
|
|
def downgrade():
|
|
op.drop_column('job_statistics', 'sent')
|
|
op.drop_column('job_statistics', 'failed')
|
|
op.drop_column('job_statistics', 'delivered')
|