#34510: sqlmigrate does not follows replaces in squashed migrations
-------------------------------------+-------------------------------------
Reporter: NeodymiumFerBore | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Management | Version: 4.2
commands) |
Severity: Normal | Resolution: invalid
Keywords: squashed migration | Triage Stage:
replaces sqlmigrate command core | Unreviewed
management |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Sanders):
* status: new => closed
* resolution: => invalid
Comment:
Hello,
Sorry I don't think there is any issue here.
The [https://docs.djangoproject.com/en/4.2/topics/migrations/#squashing-
migrations documentation] states when removing replaced migrations, the
`replaces` attributes must also be removed.
I ran a test to see if there were any issues with sqlmigrate & deleted
squashed migrations and it behaves as expected.
Closing as invalid. If there's any extra information that comes to light
or if there's something that I'm missing here feel free to add a comment
👍
--
Ticket URL: <https://code.djangoproject.com/ticket/34510#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187ad3dbe81-df497851-5e0a-4476-8c08-f3c48d08a18f-000000%40eu-central-1.amazonses.com.
