darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2025-12-13 16:52:23 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
111135a9b6a93970117f3868e4bcb5813d5b2904
notifications-api/migrations/versions/0094_job_stats_update.py

28 lines
761 B
Python
Raw Normal View History

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
"""
import sqlalchemy as sa
black, isort, flake8 Signed-off-by: Cliff Hill <Clifford.hill@gsa.gov>
2023-12-08 21:43:52 -05:00
from alembic import op
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
# revision identifiers, used by Alembic.
reformat
2023-08-29 14:54:30 -07:00
revision = "0094_job_stats_update"
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():
reformat
2023-08-29 14:54:30 -07:00
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))
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 downgrade():
reformat
2023-08-29 14:54:30 -07:00
op.drop_column("job_statistics", "sent")
op.drop_column("job_statistics", "failed")
op.drop_column("job_statistics", "delivered")
Reference in New Issue Copy Permalink