Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6467951
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T05:50:40+00:00 2026-05-25T05:50:40+00:00

In Django-South: I changed I’ve run the initial migration successfully for myapp but for

  • 0

In Django-South:
I changed I’ve run the initial migration successfully for myapp but for some reason, after I’ve made a change to my model and go to

./manage.py schemamigration myapp --auto
./manage.py migrate myapp

And I get a lot of traceback which ends in:

(1050, "Table 'my_table' already exists")

After much googling, I found and tried this:

./manage.py migrate myapp --fake

And then I proceed to migrate it, to no avail; same error.

Any suggestions?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T05:50:41+00:00Added an answer on May 25, 2026 at 5:50 am

    I just got this same error, and found this question by search.

    My problem was that my second migration I’d created using the --initial flag, i.e.

    $ ./manage.py startapp foo
    $ ./manage.py schemamigration --initial foo
    $ ./manage.py migrate foo
    

    … make some changes to foo …

    $ ./manage.py schemamigration --initial foo
    

    (oops!)

    $ ./manage.py migrate foo
    

    … and I get the error, and the migration fails because in the second migration, South is trying to create a table its already created.

    Solution

    In my migrations folder:

    $ ls foo/migrations
    0001_initial.py   0002_initial.py
    

    remove that second migration and re-export the second migration with the correct --auto flag:

    $ rm foo/migrations/0002_initial.py
    $ ./manage.py schemamigration --auto foo
    $ ./manage.py migrate foo
    

    Success!

    There may be other things that cause this error, but that was my bad!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Made some changes to my Django app's model and used South to migrate them
I had app lets say movies, with some models and initial south migration. Now
For some reason, when I add a new model and use Django South to
Django and south newbie here I need to change the encoding of a table
I am using South with Django for database migrations. In my models.py I changed
I was wondering if the following migration is possible with Django south and still
I've run into the same issue presented by the commenter here: Django South -
I'm trying to do a django-south migration to an existing application to add django-audit-log
I'm wondering about the advantages of using (django) South during heavy initial development of
short story I run ./manage.py schemamigration junk_app --initial on a completely fresh django project

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.