#34128: django re-using the name of a squashed migration leads to
CircularDependencyError
-------------------------------------+-------------------------------------
Reporter: Johannes 'fish' | Owner: nobody
Ziemke |
Type: Uncategorized | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
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 Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Thanks for this ticket, however transition of the squashed migration to a
normal migration is more complicated and requires removing the `replaces`
attribute, see [https://docs.djangoproject.com/en/dev/topics/migrations
/#squashing-migrations docs]:
> You must then transition the squashed migration to a normal migration
> - Deleting all the migration files it replaces.
> - Updating all migrations that depend on the deleted migrations to
depend on the squashed migration instead
> - **Removing the `replaces` attribute in the `Migration` class of the
squashed migration (this is how Django tells that it is a squashed
migration).**
--
Ticket URL: <https://code.djangoproject.com/ticket/34128#comment:2>
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/0107018431ad9284-d9c917ea-c4f0-4675-a9d1-f2586406bb99-000000%40eu-central-1.amazonses.com.
