Migrations ni njia ya Django ya kueneza mabadiliko unayofanya kwa models zako (kuongeza field, kuunda model) katika schema ya database — ni faili za mabadiliko ya database zinazodhibitiwa kwa version na kuzalishwa kiotomatiki. Unabadilisha models katika Python; migrations zinaweka database katika hali ya kufanana.
python manage.py makemigrations
python manage.py migrate
makemigrations inagundua mabadiliko ya model na inazalisha faili ya migration; migrate inatumia migrations zinazosubiri kwenye database halisi. Unaandika Python (mabadiliko ya model), na Django inazalisha na kuendesha SQL.
# migrations/0002_article_views.py (auto-generated)
class Migration(migrations.Migration):
dependencies = [("blog", "0001_initial")] # ordering — depends on the previous one
operations = [
migrations.AddField( # the change
model_name="article",
name="views",
field=models.IntegerField(default=0),
),
]
Migrations zina wekwa katika version control, hivyo historia ya schema ya database inafuatiliwa pamoja na code. Kila mwendelezaji na mazingira yanatumia migrations zilezile kufikia schema ileile — inayoweza kuzalishwa upya na yenye uthabiti.
✓ Schema changes are version-controlled (tracked with the code, reviewable in PRs)
✓ Reproducible — every dev/staging/production DB gets the same schema by running migrate
✓ No manual, error-prone SQL — Django generates the correct ALTER statements
✓ Reversible — many migrations can be rolled back (migrate <app> <previous>)
✓ Team-friendly — schema changes flow through the normal code-review process
python manage.py showmigrations # see which migrations are applied/pending
python manage.py sqlmigrate blog 0002 # preview the SQL a migration will run
python manage.py makemigrations --empty # a blank migration for custom/data changes
python manage.py migrate blog 0001 # roll BACK to a previous migration
Migrations can also transform DATA (e.g. populate a new field, backfill values)
via RunPython operations — useful when a schema change needs accompanying data changes.
Migrations ni muhimu kwa kufanya kazi na tabaka la database la Django — zinatatua tatizo muhimu la kuweka schema ya database katika hali ya kufanana na models zako za Python kwa njia salama, inayoweza kuzalishwa upya, na rafiki kwa timu.
Kuzielewa ni maarifa ya msingi ya kila siku: mtiririko wa makemigrations → migrate ndiyo jinsi kila mabadiliko ya schema yanavyotokea (unabadilisha models, Django inazalisha na kutumia SQL), hivyo huwezi kuendeleza programu ya Django inayoendeshwa na data bila huo.
Thamani muhimu ni kwamba migrations zinafanya mabadiliko ya schema kuwa yanayodhibitiwa kwa version (yanafuatiliwa pamoja na code, yanaweza kukaguliwa katika pull requests), yanayoweza kuzalishwa upya (kila mazingira — mashine ya kila mwendelezaji, staging, production — inafikia schema inayofanana kwa kuendesha migrations zilezile), na salama (Django inazalisha SQL sahihi, mara nyingi inayoweza kurudishwa nyuma badala ya ALTER TABLE za mkono zinazoweza kuwa na makosa).
Hii inaondoa aina nzima ya matatizo kuhusu schema drift, mazingira yasiyofanana, na mabadiliko hatari ya database ya mkono.
Kujua mtiririko, kwamba migrations zinawekwa katika source control, jinsi ya kuzikagua na kuzirudisha nyuma, na kwamba zinaweza pia kushughulikia mabadiliko ya data (kujaza/kuhamisha data, si schema tu) ni muhimu kwa mradi wowote halisi wa Django.
Migrations ndiyo jinsi timu za Django zinavyobadilisha schema ya database yao kwa ushirikiano na uthabiti katika kipindi cha maisha ya mradi, kuifanya kuwa nyenzo ya msingi na ya lazima kujua.