#15915: Permission codename duplication is not handled well
------------------------------+---------------------------------------
Reporter: valyagolev | Owner: mhaligowski
Type: Bug | Status: closed
Component: contrib.auth | Version: 1.3
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
------------------------------+---------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"8c427448d53ec0d860e1669f35deed73d0240ba1"]:
{{{
#!CommitTicketReference repository=""
revision="8c427448d53ec0d860e1669f35deed73d0240ba1"
Fixed #15915 -- Cleaned handling of duplicate permission codenames
Previously, a duplicate model, codename for permission would lead to
database integrity error. Cleaned the implementation so that this case
now raises an CommandError instead.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15915#comment:17>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
