migrations/versions/0094_job_stats_update.py

"""empty message

Revision ID: 0094_job_stats_update
Revises: 0092_add_inbound_provider
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 = '0092_add_inbound_provider'


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')
Add three new columns to job_statistics for sent, delivered and failed. 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. 2017-06-07 11:15:05 +01:00			`"""empty message`

			`Revision ID: 0094_job_stats_update`
delete some migrations 2023-07-18 13:44:38 -07:00			`Revises: 0092_add_inbound_provider`
Add three new columns to job_statistics for sent, delivered and failed. 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. 2017-06-07 11:15:05 +01:00			`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'`
delete some migrations 2023-07-18 13:44:38 -07:00			`down_revision = '0092_add_inbound_provider'`
Add three new columns to job_statistics for sent, delivered and failed. 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. 2017-06-07 11:15:05 +01:00

			`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')`