#32205: sqlmigrate crashes after removing squashed migrations.
-------------------------------------+-------------------------------------
Reporter: 老广 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: sqlmigrate | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Stian Jensen):
What is not mentioned in the CLI output, but in the documentation is the
following:
> You must then transition the squashed migration to a normal migration
by:
>
> * 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).
https://docs.djangoproject.com/en/3.2/topics/migrations/#squashing-
migrations
Did you also do that?
Maybe it should be better explained also from the CLI.
--
Ticket URL: <https://code.djangoproject.com/ticket/32205#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f765538805df448a6604041daa9c6dfb%40djangoproject.com.
