#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: Migrations | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------+------------------------
(I'd have thought we might already have a ticket for this, but I couldn't
find it.)
So far our answer here has been "sorry, you can't do it, unless you're
very familiar with the depths of the migrations system and willing to put
a lot of time into it."
I don't believe that this is a tenable or defensible answer. It puts too
many of our users, too frequently, into an impossible quandary. I think we
need to clearly document how you can do it today, even if the process is
nasty and ugly. Hopefully seeing that nasty and ugly documentation might
clarify what could be improved to make the process less nasty and ugly.
--
Ticket URL: <https://code.djangoproject.com/ticket/25313>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.bd4aeab7050bc00e540295a23a9a888a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
