Well, I don't.  But changing a database migration after it's already been run by anyone -- even just you and I -- can cause problems, so it'd be cleaner to let the addition stand, and rename it after the fact, meaning adding another database migration.  I wasn't sure that overhead was worth doing to fix a fairly minor (aesthetic) issue.  What do you think?

We could also just rename it, with the caveat that we'd all have to reset our databases (or rename the column manually).  Since it probably just affects you and I, that might be okay.