Hi, When using `add_enum_value` in an `up` block with pg_enum, what is the best practice for the `down` block?
I understand a `remove_enum_value` does not exist since it could leave rows in a corrupt state. I'm inclined to leave the `down` block empty. But then, re-running the up block and its `add_enum_value` would fail because the enum value already exists (wasn't removed by the `down` block). That leaves the migrations in a non-runnable state. So the migration is irreversible. Adding `add_enum_value?` similar to `create_table?` would provide a good-enough workaround in my use case. Is it something that can be done through pg_enum or with custom queries? Best, Michael -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/CAAkfp_Q1mw50WzR_FxMBjhgU3Pyg1H8cG5qMReeKUQxEi9FFnw%40mail.gmail.com.
