#24703: Use MigrationLoader in squashmigrations
-------------------------------------+-------------------------------------
Reporter: knbk | Owner: knbk
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Markus Holtermann <info@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"1521861b3cc07fffdbe95c41000bf8e8ef92cc6b" 1521861]:
{{{
#!CommitTicketReference repository=""
revision="1521861b3cc07fffdbe95c41000bf8e8ef92cc6b"
Fixed #24703 -- Changed squashmigrations to use a MigrationLoader
Changed squashmigrations to not instantiate a MigrationExecutor,
but to directly use a MigrationLoader instance instead.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24703#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.de0e089c03023c7997415aa1b8ac0d35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
