#25313: Document how to migrate from a built-in User model to a custom User
model
-------------------------------+------------------------------------
Reporter: Carl Meyer | Owner: nobody
Type: New feature | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | 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 David Sanders):
On the point of "Throw away all your migrations", I'd like to add a note
that some data migrations that setup fixtures may need to be kept. This
may involve extracting these operations from their respective migrations
and updating them to use the latest schema then appending them to the
resulting initial migrations generated.
--
Ticket URL: <https://code.djangoproject.com/ticket/25313#comment:14>
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/064.7c13036b8c7a1eb23e04be951b1c034d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
