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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T17:42:43+00:00 2026-05-27T17:42:43+00:00

I have updated our project from svn and I have new migration files. When

  • 0

I have updated our project from svn and I have new migration files.
When I use :

./work/manage.py schemamigration mypackage --auto

I have this message:

Nothing seems to have changed.

But the database has changed! Why south couldn’t detect any change?

Thanks in advance

  • 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-27T17:42:44+00:00Added an answer on May 27, 2026 at 5:42 pm

    If you already have the migration files, there is no need to run schemamigration as that just generates the migration files. To apply the migration files to the database, run:

    ./work/manage.py migrate mypackage --merge
    

    The merge flag will run any missed migrations as a result of an SVN update.

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

Sidebar

Related Questions

I've recently updated our MVC 2 project at work to use Areas however I'm
Whenever I update our project's code from the svn I have to set the
I want to use SvnAnt to checkout the latest code from our svn repository,
We've noticed that when checking in updates, our .DFM files have added ExplicitWidth and
I have updated my android-sdk-package from r16 to r17. I have updated the Eclipse
Okay I have updated my code quite a bit. I am getting a new
When I want to add a new feature to our project, I create a
Suppose I have tagged the release version of our project under $SVNROOT/project/tags/1.0 . Suppose
At work we use a particular in-house DLL almost everywhere. It's constantly being updated
Our project is held in a SourceSafe database. We have an automated build, which

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.