Hey Markus, Thanks for the suggestion. Added that snippet for now.
I was kind of surprised when I could not find a way to handle the backward migrations. I created a ticket - https://code.djangoproject.com/ticket/24037 For now I don't mind the migration being irreversible. But the perfect 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 from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/45da8493-5620-4547-a84b-27e7b5fb0a42%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
