I added a Postgres TIMESTAMP column and ran a migration, then realized I wanted to do TIMESTAMP(timezone=True) so I updated my models then ran another migration, but the migration files had a 'pass' in the upgrade/downgrade functions rather than doing anything. I had to revert to the migration before I added the TIMESTAMP(without time zone) columns then re-run a migration to get it to work. Just wanted to see if it was me doing something wrong or if adding a timezone to an existing TIMESTAMP isn't (yet) supported by Alembic.
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
