Fellow Report - October 28, 2017

Triaged --- https://code.djangoproject.com/ticket/28646 - Migration calls "CREATE INDEX" when one already exists when 'unique' field attribute is added (accepted) https://code.djangoproject.com/ticket/28728 - Make validate_password() require a user instance (wontfix) https://code.djang

Re: Inconsistency when rolling back a migration that adds a primary key

I've implemented a fix for this that works, in which I deleted the code that automatically drops the old primary key when a new one is added. I think this is consistent with the way it's intended to be used: if I autogenerate a migration for changing the primary key, then the old one is explicitly