Fix PostgreSQL compatibility in Alembic migrations

This commit is contained in:
A R R R Associates
2026-06-21 19:38:13 +05:30
parent b3925bd4e7
commit f2f4e0f7f8
7 changed files with 43 additions and 25 deletions
@@ -55,7 +55,7 @@ def upgrade() -> None:
sa.Column("reviewed_at_utc", sa.DateTime(timezone=True), nullable=True),
sa.Column("created_at_utc", sa.DateTime(timezone=True), nullable=False, server_default=sa.text("CURRENT_TIMESTAMP")),
sa.Column("updated_at_utc", sa.DateTime(timezone=True), nullable=False, server_default=sa.text("CURRENT_TIMESTAMP")),
sa.Column("is_active", sa.Boolean(), nullable=False, server_default=sa.text("1")),
sa.Column("is_active", sa.Boolean(), nullable=False, server_default=sa.text("true")),
)
for index_name, columns in {
@@ -77,7 +77,7 @@ def upgrade() -> None:
if _has_table(bind, "service_catalogues") and not _has_column(bind, "service_catalogues", "is_consultant_requestable"):
with op.batch_alter_table("service_catalogues") as batch_op:
batch_op.add_column(sa.Column("is_consultant_requestable", sa.Boolean(), nullable=False, server_default=sa.text("0")))
batch_op.add_column(sa.Column("is_consultant_requestable", sa.Boolean(), nullable=False, server_default=sa.text("false")))
def downgrade() -> None: