title: South won't generate or apply migrations for existing app, with changes to migrate
body: <p>I'm using South to generate and apply migrations, rather than managing that myself. Unfortunately, South is refusing to actually <em>do</em> anything. Transcript below:</p>
  
  <pre><code>[graffias:~/testing.tustincommercial.com/oneclickcos]$ python ./manage.py schemamigration mainapp --auto
  You cannot use --auto on an app with no migrations. Try --initial.
  [graffias:~/testing.tustincommercial.com/oneclickcos]$ python ./manage.py schemamigration mainapp --initial
   + Added model mainapp.CompanyUK
   + Added model mainapp.CompanyName
   + Added model mainapp.Individual
   + Added model mainapp.Director
   + Added model mainapp.DirectorsIndividual
   + Added model mainapp.DirectorsCorporate
   + Added model mainapp.ShareCapitalClass
   + Added model mainapp.Member
   + Added model mainapp.MembersIndividual
   + Added model mainapp.MemberGeneric
   + Added model mainapp.CompanyManager
   + Added model mainapp.PendingRegistration
   + Added model mainapp.PendingAuthorisation
  Created 0001_initial.py. You can now apply this migration with: ./manage.py migrate mainapp
  [graffias:~/testing.tustincommercial.com/oneclickcos]$ python ./manage.py migrate mainapp
  Running migrations for mainapp:
  - Nothing to migrate.
   - Loading initial data for mainapp.
  No fixtures found.
  [graffias:~/testing.tustincommercial.com/oneclickcos]$ 
  </code></pre>
  
  <p>As you can see, South thinks there is nothing to do. However, the last three models are completely new, and have no table in the database.</p>
  
  <p>Is there anything I can do, short of zapping the database to get South working again?</p>
  
  <p>I have no intention of manually writing migrations for the rest of the project, but if it would help, I would write one migration. </p>