Thanks, Tim. I'll take a look at this. > From the Django 1.11 release notes: > > - The prompt for stale content type deletion no longer occurs after > running the migrate command. Use the new remove_stale_contenttypes > > <https://docs.djangoproject.com/en/1.11/ref/django-admin/#django-admin-remove_stale_contenttypes> > command instead. > > In older versions of Django, stale content type deletion doesn't happen > unless you type "yes" to the prompt that happens after migrate. > > On Friday, May 5, 2017 at 8:41:18 AM UTC-4, [email protected] wrote: >> >> Hi. >> >> Why Django automatically removes content types? >> >> Due to lack of flexibility in auth system I was forced to create custom >> content type for custom perms. >> Now I've realized that my custom content type is missing. >> I am not sure, of course, but I think that Django removed my CT silently. >> >> I know that clearing content types is OK, maybe required, but it SHOULD >> NOT to be run automatically! >> Deleting the data is a risky operation and should be called on demand. >> >> Is possible to disable automatic CT deletion? >> >> >> Marcin >> >>
-- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e7128eeb-b798-49ee-a60f-400c046ff249%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
