#30351: Migration auth.0011_update_proxy_permissions fails for models recreated
as
a proxy.
---------------------------------+--------------------------------------
Reporter: Julien Enselme | Owner: Arthur Rio
Type: Bug | Status: assigned
Component: contrib.auth | Version: 2.2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Arthur Rio):
* owner: nobody => Arthur Rio
* status: new => assigned
Comment:
We do not automatically delete stale content types on purpose to avoid
data loss. When deleting a model, the `remove_stale_contenttypes.py`
management command
[https://github.com/django/django/blob/master/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py]
should be ran. We can do two things here:
1. Handle the `IntegrityError` with a helpful message to point to the
command
2. Re-use existing content types
I think 1. is safer but I am open to suggestions.
--
Ticket URL: <https://code.djangoproject.com/ticket/30351#comment:6>
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/066.2059f89e6c041064c8082a64ee93bee6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
