viktor/wrongmove
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix alembic migration to rename buylisting.longtitude to longitude

Browse source 
The migration was incorrectly changed to a no-op, leaving the typo
in the buylisting table which caused OperationalError during scraping.
This commit is contained in:
Viktor Barzin 2026-02-09 20:47:30 +00:00
parent 0fb4504646
commit f465ccb8b8
No known key found for this signature in database
GPG key ID: 0EB088298288D958
1 changed files with 4 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

10
alembic/versions/e5f1bc4e3323_fix_typo_in_logitude_column.py
View file

@ -19,12 +19,10 @@ depends_on: Union[str, Sequence[str], None] = None
def upgrade() -> None: def upgrade() -> None:
"""Upgrade schema - this migration is now a no-op since tables already have correct column name.""" """Rename 'longtitude' to 'longitude' in buylisting table."""
# The tables were created with 'longitude' (correct spelling) in the initial migration. op.alter_column('buylisting', 'longtitude', new_column_name='longitude', existing_type=sa.Float(), existing_nullable=False)
# This migration was incorrectly auto-generated and has been fixed to be a no-op.
pass
def downgrade() -> None: def downgrade() -> None:
"""Downgrade schema - no-op since upgrade is no-op.""" """Rename 'longitude' back to 'longtitude' in buylisting table."""
pass op.alter_column('buylisting', 'longitude', new_column_name='longtitude', existing_type=sa.Float(), existing_nullable=False)