id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
34416	Option start_migration_name for squashmigrations do not work properly	pepe_bokitka69	nobody	"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)?"	Uncategorized	closed	Migrations	4.1	Normal	invalid	squashmigrations start_migration_name		Unreviewed	0	0	0	0	0	0