#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 pothiers):
At the start of our first real Django project we anticipated needing
authentication eventually, so followed instructions from
https://docs.djangoproject.com/en/4.0/topics/auth/customizing
/#customizing-authentication-in-django. (we expected to use an email
address instead of username for the identification token). We basically
stubbed it until we knew what we needed. For our 2nd project we thought we
would never need authentication so did nothing relating to users. We are
now a likely to nuke our databases and rebuild to avoid the migration
complications described in this ticket.
Given the impact of customizing authentication mid-project, why doesn't
the default setup simply create an appropriate stub? Is the problem
choosing an appropriate stub? Maybe that's easier than solving migration?
--
Ticket URL: <https://code.djangoproject.com/ticket/25313#comment:28>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070186741a0243-ac693ece-725c-4801-a8f5-3804bbd7d8e7-000000%40eu-central-1.amazonses.com.
