Migrations sannan suke aiki?

Question

Accepted Answer

**Migrations** sune hanyar Django don yaɗa canje-canjen da kake bukata a cikin models (ƙara fili, aiki model) zuwa cikin **database schema** — suna da iko-iko, awtomatikman ana samar da su sunayen keɓi a cikin filin bayanai. Ka canja models a Python; migrations suna kiyaye bayanai a cikin kwatanci. ## Aiwataccen hanyoyin biyu ```bash # 1. you change a model in models.py (e.g. add a field)... # 2. generate a migration file describing the change python manage.py makemigrations # → creates migrations/0002_article_views.py (the change, as Python) # 3. apply the migration to the database python manage.py migrate # → runs the SQL to alter the database schema (ADD COLUMN, etc.) ``` `makemigrations` yana gano canje-canjen model kuma yana samar da filin migration; `migrate` yana amfani da migrations da suka jira zuwa bayanai na ainihi. Ka rubuta Python (canje-canjen model), kuma Django ta samar kuma ta aiwatar SQL. ## Filin migration shine addin da aka ƙaddara ```python # 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 suna **bugi zuwa iko-iko na ƙaddara**, saboda tarihin database schema ana raka shi tare da lambar. Kowane mai aiki da muhalli yana amfani da ƙayyade migration ɗin gida don sanin ƙayyade schema ɗin — maimaitawa kuma daidai. ## Me ya sa migrations suka matukaita (maimakon SQL na hannu) ```text ✓ 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 ) ✓ Team-friendly — schema changes flow through the normal code-review process ``` ## Halaye masu ilimi da fuddansuwa ```bash 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 ``` ## Data migrations (ba kwata-kwata schema ba) ```text 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. ``` ## Me ya sa ita ta matukaita Migrations sune mahimmanci ga aiki tare da shafi bayanai na Django — suna warware matsalar mahimmanci na kiyaye database schema a gaida tare da Python models ta karfi, maimaitawa, kuma ta careshi ido ta sadarwa. Fahimta su shine abin mahimmanci na yau da kullun: `makemigrations` → `migrate` aiwatacce shine yadda kowa schema ɗin ya canja (ka canja models, Django ta samar kuma ta aiwatar SQL), saboda ba za ka iya haɓaka bayanai-tuƙi Django app ba. Ganin mahimmaci shine migrations na sanya canje-canjen schema **iko-iko na ƙaddara** (aka raka shi tare da lambar, mai bincike a cikin sunayen bugi), **maimaitawa** (kowane muhalli — likitocin mai aiki, shiga, sakamakon sakamakon — ya isa ƙayyade schema ɗin ta aiwatar migrations ɗin) kuma **karfi** (Django ta samar daidai, sau da yawa-maimaita SQL kafai maimakon kuskure hannu `ALTER TABLE` batun). Wancan yana kawar da kategoɗin matsala dangane da schema drift, muhalli na kada-kada, kuma damje-damjèn canji na bayanai. Sanin aiwataccen hanyoyin, cewa migrations suna bugi zuwa tushe na lambar, yadda za ka iya duba kuma mayar, kuma cewa suna iya kuma sarrafa **data transformations** (baƙi/migrating bayanai, ba kwata-kwata schema ba) shine dole a kowane ainihin Django project. Migrations sune yadda Django dabbobi ke haɓaka schema bayanai su tare kuma taƙaitacce a jiya, suna sanya haka mahimmanci, sanwan-mahimmanci.