#25231: Incomplete Fix for #24628 - Squashed Migration Still Not Marked as
Applied
----------------------------+---------------------------------------------
Reporter: mlavin | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
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: 0 | UI/UX: 0
----------------------------+---------------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"69db1c745506bf63026def25d6854755179feaa8" 69db1c7]:
{{{
#!CommitTicketReference repository=""
revision="69db1c745506bf63026def25d6854755179feaa8"
Fixed #25231 -- Added recording of squashed migrations in the migrate
command.
Ensured squashed migrations are recorded as applied when the
migrate command is run and all of the original migrations
have been previously applied.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25231#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/064.a3087ccff087f33e0d2f34169c7256e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
