#25313: Document how to migrate from a built-in User model to a custom User
model
-------------------------------+------------------------------------
Reporter: carljm | 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 aaugustin):
At some point I thought it was doable with `SeparateDatabaseAndState` but
eventually I realized that it isn't.
When you change `settings.AUTH_USER_MODEL`, suddenly Django has a
different view of the migration history. Piling hacks cannot hide this
fact. I don't think it's possible to salvage migration history when
changing `AUTH_USER_MODEL`.
--
Ticket URL: <https://code.djangoproject.com/ticket/25313#comment:4>
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.27e4b2eba10b6d0c8670635732a53dd4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
