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
22863	Document that changing model options unrelated to the database will create migrations	davidray	nobody	"Django '''1.7b4''' tag

Steps to reproduce:

 * Create initial migrations for app
 * drop and recreate database
 * Run `python manage.py migrate`
 * Update a model field's `verbose_name`
 * Run `python manage.py migrate`

Output is as follows:

{{{
Running migrations:
  No migrations needed.
  Your models have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
}}}

 * Run `python manage.py makemigrations`

Generates an `AlterField` migration:

{{{
# encoding: utf8
from __future__ import unicode_literals

from django.db import models, migrations


class Migration(migrations.Migration):

    dependencies = [
        ('myapp', '0001_initial'),
    ]

    operations = [
        migrations.AlterField(
            model_name='mymodel',
            name='myfield',
            field=models.ForeignKey(verbose_name='my verbose name', to_field='id', to='myapp.MyModel'),
        ),
    ]

}}}

I did not think that a modification to `verbose_name` would necessitate a migration.








"	Cleanup/optimization	closed	Migrations	1.7-beta-2	Release blocker	fixed			Accepted	0	0	0	0	0	0