Mariusz makes the point on the ticket that this can cause data loss for custom content types, which is true.
This seems to be a fairly thorny problem to me since there are several different data loss risks. Perhaps a documentation change would be the easiest first step - one can always remove particular stale content types in a data migration. On Tue, 31 Dec 2019 at 14:20, gowtham kommineni <gowtham...@gmail.com> wrote: > Hi Adam > > Please link to the ticket here. >> > > ticket: https://code.djangoproject.com/ticket/31123 > PR: https://github.com/django/django/pull/12257 > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/e27e1fd5-9ba9-4b9d-b9a0-f477fb353769%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/e27e1fd5-9ba9-4b9d-b9a0-f477fb353769%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Adam -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM0OVRURkJtq9-mXyUgzHWMdK2JxAVxrOJdsQmipuYkVyQ%40mail.gmail.com.
