migrations/versions/0351_unique_key_annual_billing.py

"""

Revision ID: 0351_unique_key_annual_billing
Revises: 0349_add_ft_processing_time
Create Date: 2021-04-12 09:02:45.098875

"""

import os

from alembic import op

revision = "0351_unique_key_annual_billing"
down_revision = "0349_add_ft_processing_time"

environment = os.environ["NOTIFY_ENVIRONMENT"]


def upgrade():
    index = """
        CREATE UNIQUE INDEX CONCURRENTLY uix_service_id_financial_year_start
        ON annual_billing (service_id, financial_year_start)
    """
    constraint = """
        ALTER TABLE annual_BILLING add constraint uix_service_id_financial_year_start
         UNIQUE USING INDEX uix_service_id_financial_year_start
    """
    op.execute("COMMIT")
    op.execute(index)
    op.execute(constraint)


def downgrade():
    op.drop_constraint(
        "uix_service_id_financial_year_start", "annual_billing", type_="unique"
    )
Add unique key on annual_billing for service_id + financial_year_start. This is an extra precaution for the table to ensure data integrity. Since we only update/insert the data using the annual_billing_dao methods the integrity is in tact. I've check the data on preview, staging and prod there are no violations of this unique key. 2021-04-20 13:42:20 +01:00			`"""`

			`Revision ID: 0351_unique_key_annual_billing`
notify-api-56 squash migrations 2023-07-19 09:19:40 -07:00			`Revises: 0349_add_ft_processing_time`
Add unique key on annual_billing for service_id + financial_year_start. This is an extra precaution for the table to ensure data integrity. Since we only update/insert the data using the annual_billing_dao methods the integrity is in tact. I've check the data on preview, staging and prod there are no violations of this unique key. 2021-04-20 13:42:20 +01:00			`Create Date: 2021-04-12 09:02:45.098875`

			`"""`
reformat up to latest version of black 2024-04-01 15:12:33 -07:00
To avoid any table locks and contention on the production database we are going to add the unique index concurrently. This only works if we execute a commit first. 2021-04-23 15:08:23 +01:00			`import os`

Add unique key on annual_billing for service_id + financial_year_start. This is an extra precaution for the table to ensure data integrity. Since we only update/insert the data using the annual_billing_dao methods the integrity is in tact. I've check the data on preview, staging and prod there are no violations of this unique key. 2021-04-20 13:42:20 +01:00			`from alembic import op`

reformat 2023-08-29 14:54:30 -07:00			`revision = "0351_unique_key_annual_billing"`
			`down_revision = "0349_add_ft_processing_time"`
Add unique key on annual_billing for service_id + financial_year_start. This is an extra precaution for the table to ensure data integrity. Since we only update/insert the data using the annual_billing_dao methods the integrity is in tact. I've check the data on preview, staging and prod there are no violations of this unique key. 2021-04-20 13:42:20 +01:00
reformat 2023-08-29 14:54:30 -07:00			`environment = os.environ["NOTIFY_ENVIRONMENT"]`
To avoid any table locks and contention on the production database we are going to add the unique index concurrently. This only works if we execute a commit first. 2021-04-23 15:08:23 +01:00
Add unique key on annual_billing for service_id + financial_year_start. This is an extra precaution for the table to ensure data integrity. Since we only update/insert the data using the annual_billing_dao methods the integrity is in tact. I've check the data on preview, staging and prod there are no violations of this unique key. 2021-04-20 13:42:20 +01:00
			`def upgrade():`
To avoid any table locks and contention on the production database we are going to add the unique index concurrently. This only works if we execute a commit first. 2021-04-23 15:08:23 +01:00			`index = """`
freshen up files 2023-11-17 09:47:32 -05:00			`CREATE UNIQUE INDEX CONCURRENTLY uix_service_id_financial_year_start`
To avoid any table locks and contention on the production database we are going to add the unique index concurrently. This only works if we execute a commit first. 2021-04-23 15:08:23 +01:00			`ON annual_billing (service_id, financial_year_start)`
			`"""`
			`constraint = """`
			`ALTER TABLE annual_BILLING add constraint uix_service_id_financial_year_start`
			`UNIQUE USING INDEX uix_service_id_financial_year_start`
			`"""`
reformat 2023-08-29 14:54:30 -07:00			`op.execute("COMMIT")`
To avoid any table locks and contention on the production database we are going to add the unique index concurrently. This only works if we execute a commit first. 2021-04-23 15:08:23 +01:00			`op.execute(index)`
			`op.execute(constraint)`
Add unique key on annual_billing for service_id + financial_year_start. This is an extra precaution for the table to ensure data integrity. Since we only update/insert the data using the annual_billing_dao methods the integrity is in tact. I've check the data on preview, staging and prod there are no violations of this unique key. 2021-04-20 13:42:20 +01:00

			`def downgrade():`
reformat 2023-08-29 14:54:30 -07:00			`op.drop_constraint(`
			`"uix_service_id_financial_year_start", "annual_billing", type_="unique"`
			`)`