On Fri, Oct 31, 2014 at 9:46 AM, Andrew Godwin <and...@aeracode.org> wrote: > So, bear in mind that you can easily set these defaults yourself in a > migration with RunSQL if you need them for legacy purposes; that way they'll > get applied
Absolutely. I effectively have such a system in place at the moment. But, my point is I am also making an effort to match Django's expected schema while moving away from the legacy schema. I would prefer not to drift too far from Django's expectations as the goal is move entirely to Django. This is just one more thing to keep track of and handle semi-manually. All I'm saying is that if the described feature existed, it would benefit me and others that share my use case. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CADhq2b7zb4SfwTpE8AvuaCkuNLVO%3DYQoFNQZK3ks6fpR0%3DjVYA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
