#25442: RunSQL migration is run twice (and once for real with "--fake")
----------------------------+--------------------------------------
Reporter: tino | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => invalid
Comment:
I think this is a symptom of trying to migrate from the built-in auth user
to a custom user model. This currently doesn't work very well as described
in #25313.
The tracebacks are you seeing aren't a migration running, but rather the
`post_migrate` signal handler that creates user permissions.
--
Ticket URL: <https://code.djangoproject.com/ticket/25442#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/062.ee815fc2b53d2bac2787a6ef7bfdbc01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
