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 7176389
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T16:29:49+00:00 2026-05-28T16:29:49+00:00

South migrations have worked quite well until now when I think it got mixed.

  • 0

South migrations have worked quite well until now when I think it got mixed.

I always do:

manage.py schemamigration core --auto
manage.py migrate core

Last time I changed my model it has happily done the schemamigration but failed at the second step. I have executed migrate core again (not sure why) but it has thrown the same error. I then though ok, I’ll change something else and do the schemamigration again to get this back on track but this hasn’t helped and I’m now stuck:

D:\~Sasha\Portman>manage.py migrate --list

 core
  (*) 0001_initial
  (*) 0002_auto__del_field_project_is_active
  (*) 0003_auto__add_field_groups_description
  (*) 0004_auto__chg_field_project_name
  (*) 0005_auto__add_status__del_field_project_phase_indicator_resources__del_fie
  (*) 0006_auto__add_project_phase_history
  (*) 0007_auto__add_field_project_phase_project__del_field_project_project_phase
  (*) 0008_auto__chg_field_project_phase_date_end_plan
  (*) 0009_auto__del_field_project_phase_date_start_actual__del_field_project_pha
  (*) 0010_auto__del_status
  (*) 0011_auto__chg_field_project_phase_history_date_start_plan
  (*) 0012_auto__chg_field_project_link_business_idea__chg_field_project_link_cha
  (*) 0013_auto__del_field_project_project_sc_reviews
  (*) 0014_auto
  (*) 0015_auto__add_sc__del_field_sc_event_is_reviewed__del_field_sc_event_date_
  (*) 0016_auto__add_field_project_phase_is_finished
  (*) 0017_auto__del_field_project_phase_history_date_start_actual__del_field_pro
  (*) 0018_auto__del_field_project_phase_date_end_plan__del_field_project_phase_d
  (*) 0019_auto__add_field_project_phase_is_reviewed_by_pmo
  (*) 0020_auto__add_project_excel_import__add_priorities__add_field_project_is_i
  (*) 0021_auto__del_project_excel_import__add_project_imported_from_excel
  (*) 0022_auto__add_field_project_imported_from_excel_phase_date_end
  (*) 0023_auto__chg_field_project_imported_from_excel_date_end__chg_field_projec
  (*) 0024_auto__del_sc__add_sc_review_decision__add_sc_review_task__add_pmo_revi
  ( ) 0025_auto__chg_field_project_phase_phase_review_goal__chg_field_sc_review_t
  ( ) 0026_auto__del_field_project_phase_phase_review_goal__add_field_project_pha

… and trying to migrate the 0025 fires the same error:

D:\~Sasha\Portman>manage.py migrate core 0025
 - Soft matched migration 0025 to 0025_auto__chg_field_project_phase_phase_review_goal__chg_field_sc_review_t.
Running migrations for core:
 - Migrating forwards to 0025_auto__chg_field_project_phase_phase_review_goal__chg_field_sc_review_t.
 > core:0025_auto__chg_field_project_phase_phase_review_goal__chg_field_sc_review_t
Traceback (most recent call last):
  File "D:\~Sasha\Portman\manage.py", line 11, in <module>
    execute_manager(settings)
  File "D:\install\python27\lib\site-packages\django\core\management\__init__.py", line 438, in execute_manager
    utility.execute()
  File "D:\install\python27\lib\site-packages\django\core\management\__init__.py", line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "D:\install\python27\lib\site-packages\django\core\management\base.py", line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "D:\install\python27\lib\site-packages\django\core\management\base.py", line 220, in execute
    output = self.handle(*args, **options)
  File "D:\install\python27\lib\site-packages\south\management\commands\migrate.py", line 102, in handle
    delete_ghosts = delete_ghosts,
  File "D:\install\python27\lib\site-packages\south\migration\__init__.py", line 202, in migrate_app
    success = migrator.migrate_many(target, workplan, database)
  File "D:\install\python27\lib\site-packages\south\migration\migrators.py", line 215, in migrate_many
    result = migrator.__class__.migrate_many(migrator, target, migrations, database)
  File "D:\install\python27\lib\site-packages\south\migration\migrators.py", line 284, in migrate_many
    result = self.migrate(migration, database)
  File "D:\install\python27\lib\site-packages\south\migration\migrators.py", line 121, in migrate
    result = self.run(migration)
  File "D:\install\python27\lib\site-packages\south\migration\migrators.py", line 95, in run
    return self.run_migration(migration)
  File "D:\install\python27\lib\site-packages\south\migration\migrators.py", line 77, in run_migration
    migration_function()
  File "D:\install\python27\lib\site-packages\south\migration\migrators.py", line 56, in <lambda>
    return (lambda: direction(orm))
  File "D:\~Sasha\Portman\core\migrations\0025_auto__chg_field_project_phase_phase_review_goal__chg_field_sc_review_t.py", line 12, in forwards
    db.rename_column('core_project_phase', 'phase_review_goal', 'phase_review_goal_id')
  File "D:\install\python27\lib\site-packages\south\db\sqlite3.py", line 128, in rename_column
    self._remake_table(table_name, renames={old: new})
  File "D:\install\python27\lib\site-packages\south\db\sqlite3.py", line 73, in _remake_table
    ", ".join(["%s %s" % (self.quote_name(cname), ctype) for cname, ctype in definitions.items()]),
  File "D:\install\python27\lib\site-packages\south\db\generic.py", line 134, in execute
    cursor.execute(sql, params)
  File "D:\install\python27\lib\site-packages\django\db\backends\util.py", line 34, in execute
    return self.cursor.execute(sql, params)
  File "D:\install\python27\lib\site-packages\django\db\backends\sqlite3\base.py", line 234, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.DatabaseError: table "_south_new_core_project_phase" already exists

Is there a way to fix this now? 🙁

  • 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-28T16:29:50+00:00Added an answer on May 28, 2026 at 4:29 pm

    The only way I’ve seen how to fix this is to manually get the database and models in sync without using south and then create brand new migrations. Here’s a good explanation:

    What's the recommended approach to resetting migration history using Django South?

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

Sidebar

Related Questions

In every generated migration files by South manage.py schemamigration, there usually will be a
I have a problem with south migrations. I still don't understand how this did
I have around fifty migrations in my store app, some of them are schemamigration
Does django-reversion work well with south migrations? Are django-reversion and south compatible? Current versions:
I'm playing around with Django South, and have been impressed by it's power, but
I have this query. It matches anything which has South in its name. But
I have a django app with four models in it. I realize now that
I'm trying to get started with South data migrations. I found this SO question:
I cannot seem to get this working. I need South to do migrations for
I have successfully synced my database using south on the local server. I am

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.