Separate the column type change and index creation for MessageLog.priority

[tim-schilling]

Closes #115.

Changes proposed in this PR:

• Separate the column type change and index creation for MessageLog.priority

[coveralls]

Coverage increased (+21.0%) to 71.762% when pulling 0b34342 on tim-schilling:postgres-django-2-upgrade into f78db66 on pinax:master.

[spookylukey]

Thanks, LGTM.

[davidszotten]

any chance of a point release with this fix? i've also come across it. one thing i noticed is that, like in the #115 my index name also doesn't have the hash (mailer_messagelog_priority_like vs mailer_messagelog_priority_5e712cf3_like). i wonder if these are old index names from South (my project's been around for a while)

comparing the output of sqlmigrate, with this patch i also get DROP INDEX IF EXISTS "mailer_messagelog_priority_like"; as opposed to only DROP INDEX IF EXISTS "mailer_messagelog_priority_5e712cf3_like"; without, which of course leaves our old-style-named indexes around which then makes pg upset when changing the column type

[spookylukey]

@davidszotten I've pushed a release now, 2.0.1

Most likely for your case you'll have to manually drop that index first, it should be a problem. I don't know there is much I can do about that.

[davidszotten]

no, this patch fixes it. i'm still digging through django source to understand exactly why, but having a step that removes db_index, django does figure out how to delete the index without the hash in the name

[davidszotten]

forgot to say, thanks!