#29843: Create permissions using migration operations rather than using the
post_migrate signal
-------------------------------------+-------------------------------------
Reporter: Petter Strandmark | Owner: Arthur
Type: | Rio
Cleanup/optimization | Status: assigned
Component: contrib.auth | Version: dev
Severity: Normal | Resolution:
Keywords: contenttypes | Triage Stage: Accepted
permissions post_migrate |
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
Replying to [comment:18 Javier Buzzi]:
> Am I missing something thing here?
>
I think your suggested edits make sense as a workaround, but I take the
point of the report to be that you have to know to call `get_or_create()`,
and this detail wouldn't be evident until zipping through an entire set of
migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/29843#comment:19>
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/0107019bbe579b36-9f95a5e0-e846-4392-89e1-35ffbf783366-000000%40eu-central-1.amazonses.com.
