#34416: Option start_migration_name for squashmigrations do not work properly
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
pepe_bokitka69 |
Type: | Status: new
Uncategorized |
Component: | Version: 4.1
Migrations | Keywords: squashmigrations
Severity: Normal | start_migration_name
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi!
I have a set of migrations for app `my_app`:
0001_initial.py
0002_auto_20180119_1100.py
0003_auto_20180119_1200.py
0003_auto_20180119_1300.py
0004_auto_20180119_1400.py
0005_auto_20180119_1500.py
The most important part is the 4 digits number from name, for example:
0003
So, I want to squash from 0003_auto_20180119_1300 to
0005_auto_20180119_1500
I write: manage.py squashmigrations my_app 0003_auto_20180119_1300 0005
But Django squashes from 0003_auto_20180119_1200 to
0005_auto_20180119_1500.
As I understand squashmigrations command works with first 4 digits from
migration name, so picks the first migration with that digits.
Is it that correct? Is it possible to use the entire name (e.g.
0003_auto_20180119_1300)?
--
Ticket URL: <https://code.djangoproject.com/ticket/34416>
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/01070186e62062dc-d151f16a-fca5-4c46-bb5b-5f2dbf4e961f-000000%40eu-central-1.amazonses.com.
