#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
---------------------------------+--------------------------------------
Comment (by Arthur Rio):
Yes it is the same issue. My recommendation to let the users figure it out
with a helpful message still stands even if it may sound a bit painful,
because:
1. It prevents data loss (we don't do an automatic delete/create of
permissions)
2. It prevents security oversights (we don't re-use an existing
permission)
3. It shouldn't happen for most use cases
Again, I would love to hear some feedback or other alternatives.
--
Ticket URL: <https://code.djangoproject.com/ticket/30351#comment:8>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.dff1a1b800b9abbca79c2debd96c6f87%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
