#28481: migrate --fake produces stale content type warning when CreateModel 
exists
in non-initial migration
----------------------------+--------------------------------------
     Reporter:  Amanda Ng   |                    Owner:  nobody
         Type:  Bug         |                   Status:  closed
    Component:  Migrations  |                  Version:  1.10
     Severity:  Normal      |               Resolution:  fixed
     Keywords:              |             Triage Stage:  Unreviewed
    Has patch:  0           |      Needs documentation:  0
  Needs tests:  0           |  Patch needs improvement:  0
Easy pickings:  0           |                    UI/UX:  0
----------------------------+--------------------------------------
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I guess this is fixed in Django 1.11 because (quoting the 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`
 command instead." (#24865)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28481#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.b7e19bc4c0731c5006991fe05b7c94ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to