title: Schema Migration after dropping table
body: <p>I added a column to my <code>models.py</code> and it was giving me issues.  On the road to trying to solve the problems I've done a couple things.</p>
  
  <ol>
  <li><strong>Dropped the table</strong>: <code>./manage.py sqlclear app | ./manage.py dbshell</code></li>
  <li><strong>Tried to "reset" the schema</strong>: <code>./manage.py schemamigration app --initial</code></li>
  <li><strong>Tried to migrate</strong>: <code>./manage.py migrate app</code></li>
  </ol>
  
  <p>After doing all these things, I get this error after trying to migrate:</p>
  
  <pre><code>FATAL ERROR - The following SQL query failed: CREATE TABLE "projects_project" ("id" integer NOT NULL PRIMARY KEY)
  The error was: table "projects_project" already exists
  </code></pre>
  
  <p>Question:  How do I repair my database?  I don't care about any of the data in the db.</p>
  
  <p><strong>Edit:</strong></p>
  
  <p>One of the related posts took me to this link <a href="https://stackoverflow.com/questions/3090648/django-south-table-already-exists?rq=1">Django South - table already exists</a> .  Apparently if you fake the migration all is well.</p>
  
  <pre><code>./manage.py migrate myapp --fake
  </code></pre>
  
  <p>I'm still unsure of all the reprocussions of this but I guess thats what docs are for.</p>