#23822: Serialize model managers in migrations
-----------------------------+---------------------
Reporter: MarkusH | Owner: MarkusH
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+---------------------
Right now it's impossible to use e.g. the `UserManager` in a `RunPython`
operation, thus `User.objects.create_superuser()` isn't available. We
should serialize the model managers into migrations too. I suggest to do
it the same way as with callable argument values on fields like
`upload_to`: the manager need to stay around as long as there is a
migration referencing it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23822>
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/050.3eb5d65767cde168c7e8a325df795851%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
