Internal use of `execute` preventing `change` autoreversibility about strong_migrations HOT 3 CLOSED

Wow, @ankane, great response time.

I took another look. add_column isn't actually an issue since the only place postgresql_version is called is wrapped in a conditional for unless direction == :down: https://github.com/ankane/strong_migrations/blob/master/lib/strong_migrations/migration.rb#L17

You'll want to be careful checking the version in future, though.

from strong_migrations.

          This migration uses execute, which is not automatically reversible.
          To make the migration reversible you can either:
          1. Define #up and #down methods in place of the #change method.
          2. Use the #reversible method to define reversible behavior.

from strong_migrations.

Hey @DylanReile, thanks for reporting 👍 I was able to reproduce and fix the issue with add_index and auto_analyze, but not sure how to reproduce the add_column one. Can you give an example migration that fails to reverse?

from strong_migrations.