migrations/versions/0193_add_ft_billing_timestamps.py

"""

Revision ID: 0193_add_ft_billing_timestamps
Revises: 0192_drop_provider_statistics
Create Date: 2018-05-22 10:23:21.937262

"""
import sqlalchemy as sa
from alembic import op

revision = "0193_add_ft_billing_timestamps"
down_revision = "0192_drop_provider_statistics"


def upgrade():
    op.add_column("ft_billing", sa.Column("updated_at", sa.DateTime(), nullable=True))
    op.add_column("ft_billing", sa.Column("created_at", sa.DateTime(), nullable=True))


def downgrade():
    op.drop_column("ft_billing", "created_at")
    op.drop_column("ft_billing", "updated_at")
Add timestamp columns to ft_billing table Added `created_at` and `updated_at` to the `ft_billing` table - having these columns makes it easier to track down issues with the data in this table. `created_at` is nullable initially, but will be changed to non-nullable once the column is populated and the DAO etc. have been updated. 2018-05-22 14:19:51 +01:00			`"""`

			`Revision ID: 0193_add_ft_billing_timestamps`
			`Revises: 0192_drop_provider_statistics`
			`Create Date: 2018-05-22 10:23:21.937262`

			`"""`
			`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 timestamp columns to ft_billing table Added `created_at` and `updated_at` to the `ft_billing` table - having these columns makes it easier to track down issues with the data in this table. `created_at` is nullable initially, but will be changed to non-nullable once the column is populated and the DAO etc. have been updated. 2018-05-22 14:19:51 +01:00
reformat 2023-08-29 14:54:30 -07:00			`revision = "0193_add_ft_billing_timestamps"`
			`down_revision = "0192_drop_provider_statistics"`
Add timestamp columns to ft_billing table Added `created_at` and `updated_at` to the `ft_billing` table - having these columns makes it easier to track down issues with the data in this table. `created_at` is nullable initially, but will be changed to non-nullable once the column is populated and the DAO etc. have been updated. 2018-05-22 14:19:51 +01:00

			`def upgrade():`
reformat 2023-08-29 14:54:30 -07:00			`op.add_column("ft_billing", sa.Column("updated_at", sa.DateTime(), nullable=True))`
			`op.add_column("ft_billing", sa.Column("created_at", sa.DateTime(), nullable=True))`
Add timestamp columns to ft_billing table Added `created_at` and `updated_at` to the `ft_billing` table - having these columns makes it easier to track down issues with the data in this table. `created_at` is nullable initially, but will be changed to non-nullable once the column is populated and the DAO etc. have been updated. 2018-05-22 14:19:51 +01:00

			`def downgrade():`
reformat 2023-08-29 14:54:30 -07:00			`op.drop_column("ft_billing", "created_at")`
			`op.drop_column("ft_billing", "updated_at")`