#36793: Reverting a model rename in an environment with pre-Django 6.0
permission
records leaves wrong users & groups associated
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Artyom
| Kotovskiy
Type: Bug | Status: assigned
Component: contrib.auth | Version: 6.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Antoliny):
I think only user 2 should have the permission, and raising an error would
be appropriate.
From the perspective of the person performing this operation, they would
naturally expect user 2 to have the permission (considering the intent of
#27489).
It feels strange that ghost data created by a bug would come back into
play.
When an error occurs, it would help the developer become aware of the
issue.
I'm also curious to hear others' opinions :)
--
Ticket URL: <https://code.djangoproject.com/ticket/36793#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b0fc59dd8-66fd3da6-2c7c-4849-9f06-aa01c901debd-000000%40eu-central-1.amazonses.com.
