From 883f765ca03ecbb28f429e03a0cba3a98cb190d2 Mon Sep 17 00:00:00 2001 From: Viet Than Date: Thu, 20 Jul 2023 21:32:45 -0400 Subject: [PATCH] SQLAlchemy Integer vs INTEGER --- ...1_52_50_7ae4658467d7_change_created_utc_to_datetimez_for_.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migrations/versions/2023_07_09_21_52_50_7ae4658467d7_change_created_utc_to_datetimez_for_.py b/migrations/versions/2023_07_09_21_52_50_7ae4658467d7_change_created_utc_to_datetimez_for_.py index d35c61e40..14c2c4bed 100644 --- a/migrations/versions/2023_07_09_21_52_50_7ae4658467d7_change_created_utc_to_datetimez_for_.py +++ b/migrations/versions/2023_07_09_21_52_50_7ae4658467d7_change_created_utc_to_datetimez_for_.py @@ -40,7 +40,7 @@ def downgrade(): """ Downgrade will truncate the milliseconds. """ - op.add_column(table_name, sa.Column('created_utc', sa.INTEGER(), server_default=sa.text('0'), nullable=True)) + op.add_column(table_name, sa.Column('created_utc', sa.Integer(), server_default=sa.text('0'), nullable=True)) op.execute(f""" UPDATE {table_name} SET created_utc =