#30351: Migration auth.0011_update_proxy_permissions from Django 2.2 fails to
apply
--------------------------------+--------------------------------------
Reporter: Julien Enselme | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 2.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by Sébastiaan Versteeg):
To get into the situation where you already have permissions with the
content type you should be able to do the following:
- Start on Django <2.2
- Create a model called 'TestModel'
- Migrate
- Delete the model called 'TestModel'
- Add a new **proxy** model called 'TestModel'
- Migrate
- Update to Django >=2.2
- Migrate
We think this is what happened in our case where we found this issue
(https://sentry.thalia.nu/share/issue/68be0f8c32764dec97855b3cbb3d8b55/).
We have a proxy model with the same name that a previous non-proxy model
once had. This changed during a refactor and the permissions for the
original model still exist.
Our solution will probably be removing the existing permissions from the
table, but that's really only a workaround.
--
Ticket URL: <https://code.djangoproject.com/ticket/30351#comment:3>
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.c3e480b3a19999030d7f10c234d375a7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
