Understanding Migrations in Django

1
Understanding Migrations in Django
2

• Django's migration system is a powerful tool for
  managing changes to your database schema over
  time. However, there are instances where you may
  need more control over the migration process,
  especially when dealing with complex scenarios or
  debugging issues. This is where fake migrations
  come into play. In this article, we'll explore
  what fake migrations are, why they are useful,
  and provide practical examples to demonstrate
  their usage in Django projects.
• Understanding Migrations in Django Before we
  dive into fake migrations, let's review the
  basics of Django migrations. Migrations are
  Python files generated by Django's makemigrations
  command, which represent changes to your models.
  These changes can include creating new models,
  altering existing ones, or deleting them. When
  you run migrate, Django applies these migrations
  to the database, ensuring that your database
  schema matches the structure defined in your
  Django models.
• https//erpsolutions.oodles.io/developer-blogs/Und
  erstanding-Migrations-in-Django/

3

• What are Fake Migrations? Fake migrations allow
  you to mark migrations as applied to the database
  without actually executing the SQL commands
  associated with them. This can be useful in
  scenarios where you want to skip applying certain
  migrations temporarily or resolve dependency
  issues between migrations.
• Example 1 Resolving Dependency Issues Suppose
  you have two migrations, 0001_initial.py and
  0002_auto_20220318.py, where 0002_auto_20220318.py
  depends on 0001_initial.py. However, you realize
  that you need to make changes to 0001_initial.py
  before applying 0002_auto_20220318.py. In this
  case, you can use a fake migration to mark
  0001_initial.py as applied without executing it