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
25690	Migration operations should be ordered to prevent all columns from being removed	Matthew Crowson	nobody	"When a migration contains changes to all fields, and a removal of the pk field and the addition of a new pk field, the migration fails. This is due to the migrations removals before the additions. This yields the warning that an empty table should be dropped before the new fields can be added. 

django.db.utils.OperationalError: (1090, ""You can't delete all columns with ALTER TABLE; use DROP TABLE instead"")

By moving the migration commands I was able to get the migration to perform successfully. 
First: Remove the existing pk
Second: Add the new pk
Lastly: the migration commands as they were initially created."	Bug	closed	Migrations	1.8	Normal	duplicate	mysql		Unreviewed	0	0	0	0	0	0