I have opened a pull request: https://github.com/django/django/pull/8924
Andrew and I came up with a good solution for migrations, together at DjangoCon. On Wednesday, June 14, 2017 at 7:36:36 AM UTC-7, Melvyn Sopacua wrote: > > On Friday 09 June 2017 15:59:50 Kenneth Reitz wrote: > > > However, it should also be noted that those same larger applications > > > are the ones that are likely to run into this problem eventually, so > > > perhaps forcing the migration is the best path moving forward. > > > > > > Existing models are the problem. Then again the database knows the truth. > So with a little inspection during apps.get_models we might be able to do > the right thing and even allow migrating in steps. > > > > Apps is also the place to mark an app as migrated. > > > > In fact - couldn't an AppConfig grow a method "get_autoid_type()" and > inject the right one? > > > > You asked fr thoughts, so there's my 2c stream. > > -- > > Melvyn Sopacua > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e3effc41-10e1-42e2-9037-84c98217cd91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
