#22788: Custom migration operations are rewritten incorrectly
----------------------------+------------------------------------
Reporter: schinckel | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"2dba6ab767d8532df5f9ea2b58325ef823d3c6f8"]:
{{{
#!CommitTicketReference repository=""
revision="2dba6ab767d8532df5f9ea2b58325ef823d3c6f8"
[1.7.x] Fixed #22788 -- Ensured custom migration operations can be
written.
This inspects the migration operation, and if it is not in the
django.db.migrations module, it adds the relevant imports to the
migration writer and uses the correct class name.
Backport of bb39037fcb from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22788#comment:12>
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/067.accd012b12606cf907cba53c6075bc49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
