Re: Migrations force me to have, forever, any name/reference I use in field validators=, choices=, whatever, valid forever (even if the requirements change).

Hi all,

Am 26.02.2015 um 13:54 schrieb Tim Graham:
> Yes, it's expected behavior. Please see the documentation on the topic:
> https://docs.djangoproject.com/en/stable/topics/migrations/#historical-models

I have not yet tried this, but won't squashing migrations as a side
effect also get us rid of dependencies of historical models?

Best regards,
Carsten

--
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+unsubscribe@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/54EF3EAE.3040004%40cafu.de.
For more options, visit https://groups.google.com/d/optout.