#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 johanneswilm):
Is anyone working on fixing this in Django itself? The workarounds may
work in a lot of cases, but when you have an application set up to rely on
the Django migration system for any database change and have it deployed
on thousands of servers that are not under your direct control, it is
somewhat useless.
Would it not be possible to create one special type of migration for this
purpose? Maybe something as simple as let the migration that creates the
user model check wither `auth.User` has been in use, and if so, copy over
entries from there.
--
Ticket URL: <https://code.djangoproject.com/ticket/25313#comment:23>
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/064.d9d3055a85e262ec0148c5819507abd4%40djangoproject.com.
