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
32834	DEFAULT_AUTO_FIELD should allow for diable migration for existing models	qiu-lijie	nobody	"DEFAULT_AUTO_FIELD new in 3.2 will change existing models' pk to BigAutoField, as BigAutoField is the default for new projects. I believe there should be an option to disable this behaviour, i.e., not migrate existing models to BigAutoField. While I understand Django wants to move away AutoField and towards BigAutoField for pk, the current behaviour will make migrations for third-party apps, which is not desirable. Ideally, all third-party apps would also migrate their own models to use BigAutoField, but we all know that some don't get maintained as much, see examples below. 

{{{
Migrations for 'account':
  /usr/local/lib/python3.8/site-packages/allauth/account/migrations/0003_auto_20210610_0705.py
    - Alter field id on emailaddress
    - Alter field id on emailconfirmation
Migrations for 'cities_light':
  /usr/local/lib/python3.8/site-packages/cities_light/migrations/0011_auto_20210610_0705.py
    - Alter field id on city
    - Alter field id on country
    - Alter field id on region
    - Alter field id on subregion
}}}
"	New feature	closed	Migrations	3.2	Normal	invalid	DEFAULT_AUTO_FIELD		Unreviewed	0	0	0	0	0	0