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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T08:57:56+00:00 2026-05-23T08:57:56+00:00

I am using South for database migration for a Django project. And I was

  • 0

I am using South for database migration for a Django project. And I was wondering if it is a good idea to commit the migration scripts that were generated by my dev server to the repository & then reusing it on the production server?

  • 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-23T08:57:56+00:00Added an answer on May 23, 2026 at 8:57 am

    Yes. That is the point of migrations to allow you to develop and test database schema changes and then deploy in test and production in a reproducible way.

    I wouldn’t consider it reuse so much as developed and tested in development and then deployed on production.

    Make sure you also develop and test backward migrations to ensure you can retreat.

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

Sidebar

Related Questions

I'm using South for migration in my Django project. When I run Pylint on
I am building an application using django, and using django-south for the database schema
I'm wondering about the advantages of using (django) South during heavy initial development of
I'm writing a migration using Django's South, and it can only work on MySQL
I'm using South with a Postgresql DB for a Django project. There is a
I have an existing Django project that has several models using concrete inheritance of
I have a drop down list that is dynamically generated using a mySQL database
i'm writing a data migration using south... but the question refers to the use
I'm currently using Django evolutions to manage my product's database evolutions. It's not perfect
I am using a legacy database which does a couple things that make sense

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.