The question is simple: How to override or disable migration within a heme.

Heme: Payola

Migration: 20150930164135_add_tax_percent_to_payola_subscriptions.rb

This field already exists. It is impossible to delete, as in it the necessary data.

  • Fork a gem, change everything you need in your version and use it. Periodically update the fork. Well, or rename the field in your application - Vasilisa
  • @ Vasilisa Yes you are right. But I would like to find a solution at the level of migrations. Temporarily (probably forever) I rename the tax_percent conflict field for the duration of the heme migrations. Thanks anyway. - exvayn
  • 2
    There is a tricky workaround - to make a migration that will add a dummy migration record from the heme to the table with the applied migrations so that its real launch will be skipped; and apply your own changes yourself. But this is dangerous, since if a list is made before the migration is applied, this mechanism will fail immediately when all migrations are applied. But in a controlled environment, where you can add this entry and then add a gem in different releases, it will work. - D-side

0