title: Django-migrations in Django 1.7 detects model changes but does not apply them on migrate
body: <p>I have been trying to synchronize changes to a model in a Django app using migrations in 1.7 (postgres 9.1 - let me know if you need more details of my environment), but manage.py migrate doesn't seem to do anything, and sqlmigrate doesn't emit any SQL. </p>
  
  <p>I thought <a href="https://stackoverflow.com/questions/25958708">Django 1.7 - &quot;No migrations to apply&quot; when run migrate after makemigrations</a> might be applicable to my situation, and I did find some history in the django_migrations table in my database. I deleted the records for the app I am trying to migrate.</p>
  
  <p>Recently I gave up on getting the alter table statements to generate/run and dropped the original version of the table. And while manage.py migrate states it is applying the migration, nothing happens to the database.</p>
  
  <p>Here are the steps I've been trying:</p>
  
  <p>Delete the history.</p>
  
  <pre><code>rm -r myapp/migrations
  ../manage.py dbshell
  myapp_db=&gt; delete from django_migrations where app='myapp'
  </code></pre>
  
  <p>Create an initial migration.</p>
  
  <pre><code>cp myapp/models.py.orig myapp/models.py
  ../manage.py makemigrations myapp
  ../manage.py migrate
  </code></pre>
  
  <p>manage.py migrate returns the following:</p>
  
  <pre><code>....
  Running migrations:
    Applying myapp.0001_initial... FAKED
  </code></pre>
  
  <p>Then I swap in the new models and generate a new migration.</p>
  
  <pre><code>cp myapp/models.py.new myapp/models.py
  ../manage.py makemigrations myapp
  </code></pre>
  
  <p>The result of makemigrations is in myapp/migrations/0002_notificationlog.py:</p>
  
  <pre><code># -*- coding: utf-8 -*-
  from __future__ import unicode_literals
  
  from django.db import models, migrations
  
  
  class Migration(migrations.Migration):
  
      dependencies = [
          ('myapp', '0001_initial'),
      ]
  
      operations = [
          migrations.CreateModel(
              name='NotificationLog',
              fields=[
                  ('id', models.AutoField(verbose_name='ID', serialize=False, auto_created=True, primary_key=True)),
                  ('tstamp', models.DateTimeField(help_text=b'Log time', auto_now_add=True)),
                  ('recipient', models.CharField(max_length=100)),
                  ('subject', models.TextField()),
              ],
              options={
              },
              bases=(models.Model,),
          ),
      ]
  </code></pre>
  
  <p>Run this migration:</p>
  
  <pre><code>../manage.py migrate
  </code></pre>
  
  <p>manage.py migrate acts like everything is OK:</p>
  
  <pre><code>....
  Running migrations:
    Applying myapp.0002_notificationlog... OK
  </code></pre>
  
  <p>I can see the log entries appear in django_migrations, but the table is not created.</p>
  
  <p>I'm lost. Any idea what to try next?</p>
  
  <p><strong>Update</strong></p>
  
  <p>When running migrate -v 3 as requested, I see </p>
  
  <pre><code>Running pre-migrate handlers for application auth
  </code></pre>
  
  <p>followed by a similar line for each installed app.</p>
  
  <p>Then</p>
  
  <pre><code>Loading 'initial_data' fixtures...
  Checking '/var/www/environment/default/myproj/myproj' for fixtures...
  No fixture 'initial_data' in '/var/www/environment/default/myproj/myproj'.
  </code></pre>
  
  <p>repeated a total of 13 times, the number of unmanaged apps.</p>
  
  <p>Then</p>
  
  <pre><code>Running migrations:
    Applying myapp.0001_initial... FAKED
  </code></pre>
  
  <p>followed by</p>
  
  <pre><code>Running post-migrate handlers for application auth
  </code></pre>
  
  <p>with a similar line for each installed app.</p>
  
  <p>For migration 0002, the output is the same, except for</p>
  
  <pre><code>Running migrations:
    Applying myapp.0002_notificationlog... OK
  </code></pre>
  
  <p>Note also that sqlmigrate doesn't output anything either:</p>
  
  <pre><code>../manage.py sqlmigrate myapp 0002 -v 3
  </code></pre>
  
  <p>Produces nothing at all.</p>
  
  <p><strong>Update 2</strong></p>
  
  <p>I copied myapp into a new project and was able to run migrations on it, but migrations stopped working when I imported my main project settings. Are there settings I should be aware of that could affect migration execution, particularly if I've been using South with previous versions of Django? </p>