#33583: sqlmigrate crashes on replaces to nonexistent migration.
-------------------------------------+-------------------------------------
Reporter: Amin Shah Gilani | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: sqlmigrate, | Triage Stage:
migrate, squash | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: David Wobrock (added)
* resolution: => invalid
* status: new => closed
* component: Uncategorized => Migrations
Comment:
Thanks for the report, this behavior was changed in
d88365708c554efe3c786c3be6da1d9de916360f. However, `replaces` is
documented and supported only for
[https://docs.djangoproject.com/en/stable/topics/migrations/#squashing-
migrations squashing migrations] so described flow was never officially
supported.
--
Ticket URL: <https://code.djangoproject.com/ticket/33583#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017f9b889afd-fc3502de-7bfe-4768-acd5-fc002238e0e6-000000%40eu-central-1.amazonses.com.
