Re: How to make a migration irreversible [1.7]

rfect solution would be a way to write my own backward migration so that I can tell it to not drop my database and not make the whole migration chain broken. Thanks, Bibhas -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe

How to make a migration irreversible [1.7]

be dropped anyway, right? Because it's the revert operation of CreateTable. How do I stop the backward migration for this particular migration? There is nothing much important before it, so it's not a trouble if it's irreversible. Am I missing something really obvious? Thanks, Bibh