operations<\/code> – a list of declarative instructions that are executed in the exact order as defined. Django converts each instruction to an SQL statement and executes it on a database schema.<\/li><\/ul>\n\n\n\nDjango migrations through examples<\/h2>\n\n\n\n Enough theory, let\u2019s dive into the real-life examples of working with migrations. I\u2019ll show you how you can create migrations, apply them and even revert them.<\/p>\n\n\n\n
Before going further, let\u2019s just set up the stage for the show. We\u2019ll start with the project structure that looks like this:<\/p>\n\n\n\n
libraryproject\/\n\u251c\u2500 library\/\n\u2502 \u251c\u2500 migrations\/\n\u2502 \u2502 \u251c\u2500 __init__.py\n\u2502 \u251c\u2500 admin.py\n\u2502 \u251c\u2500 apps.py\n\u2502 \u251c\u2500 models.py\n\u2502 \u251c\u2500 tests.py\n\u2502 \u251c\u2500 views.py\n\u2502 \u251c\u2500 __init__.py\n\u251c\u2500 libraryproject\/\n\u2502 \u251c\u2500 asgi.py\n\u2502 \u251c\u2500 settings.py\n\u2502 \u251c\u2500 urls.py\n\u2502 \u251c\u2500 wsgi.py\n\u2502 \u251c\u2500 __init__.py\n\u251c\u2500 manage.py\n<\/pre>\n\n\n\nYou can see that inside the libraryproject<\/code> there\u2019s an app called library<\/code>. It will be used for a simple demonstration of migrations. Make sure to include the library app in the INSTALLED_APPS<\/code> inside libraryproject\/settings.py<\/code>.<\/p>\n\n\n\nCreating migrations<\/h3>\n\n\n\n When you start a new project like this one, you should first run migrate<\/code> command to apply the initial migrations<\/strong> required by the default Django apps.<\/p>\n\n\n\n$ python manage.py migrate\nOperations to perform:\n Apply all migrations: admin, auth, contenttypes, sessions\nRunning migrations:\n Applying contenttypes.0001_initial... OK\n Applying auth.0001_initial... OK\n Applying admin.0001_initial... OK\n Applying admin.0002_logentry_remove_auto_add... OK\n Applying admin.0003_logentry_add_action_flag_choices... OK\n Applying contenttypes.0002_remove_content_type_name... OK\n Applying auth.0002_alter_permission_name_max_length... OK\n Applying auth.0003_alter_user_email_max_length... OK\n Applying auth.0004_alter_user_username_opts... OK\n Applying auth.0005_alter_user_last_login_null... OK\n Applying auth.0006_require_contenttypes_0002... OK\n Applying auth.0007_alter_validators_add_error_messages... OK\n Applying auth.0008_alter_user_username_max_length... OK\n Applying auth.0009_alter_user_last_name_max_length... OK\n Applying auth.0010_alter_group_name_max_length... OK\n Applying auth.0011_update_proxy_permissions... OK\n Applying auth.0012_alter_user_first_name_max_length... OK\n Applying sessions.0001_initial... OK<\/pre>\n\n\n\nThe newly created database should have all the following tables listed.<\/p>\n\n\n\nNow let\u2019s open library\/models.py<\/code> and add our new Book model there.<\/p>\n\n\n\nfrom django.db import models\n\nclass Book(models.Model):\n title = models.CharField(max_length=255)\n description = models.TextField()\n published_date = models.DateTimeField()<\/pre>\n\n\n\nAfter you add the Book model to models.py<\/code>, run makemigrations<\/code> command to generate a migration file.<\/p>\n\n\n\n$ python manage.py makemigrations\nMigrations for 'library':\n library\\migrations\\0001_initial.py\n - Create model Book<\/pre>\n\n\n\nDescription in a terminal says that a new migration file was created at library\/migrations\/0001_initial.py<\/code> and its purpose is to create a Book model.<\/p>\n\n\n\nAnd indeed, if we look at the project structure again, there\u2019s a new file in the library\/migrations<\/code> directory.<\/p>\n\n\n\nlibraryproject\/\n\u251c\u2500 library\/\n\u2502 \u251c\u2500 migrations\/\n\u2502 \u2502 \u251c\u2500 0001_initial.py\n\u2502 \u2502 \u251c\u2500 __init__.py\n\u2502 \u251c\u2500 admin.py\n\u2502 \u251c\u2500 apps.py\n\u2502 \u251c\u2500 models.py\n\u2502 \u251c\u2500 tests.py\n\u2502 \u251c\u2500 views.py\n\u2502 \u251c\u2500 __init__.py\n\u251c\u2500 libraryproject\/\n\u2502 \u251c\u2500 asgi.py\n\u2502 \u251c\u2500 settings.py\n\u2502 \u251c\u2500 urls.py\n\u2502 \u251c\u2500 wsgi.py\n\u2502 \u251c\u2500 __init__.py\n\u251c\u2500 manage.py\n<\/pre>\n\n\n\nLet\u2019s take a look how this newly created migration file looks like.<\/p>\n\n\n\n
from django.db import migrations, models\n\nclass Migration(migrations.Migration):\n\n initial = True\n\n dependencies = [\n ]\n\n operations = [\n migrations.CreateModel(\n name='Book',\n fields=[\n ('id', models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')),\n ('title', models.CharField(max_length=255)),\n ('description', models.TextField()),\n ('published_date', models.DateTimeField()),\n ],\n ),\n ]<\/pre>\n\n\n\nThere are three attributes in the current migration file. The first one, initial=True<\/code>, means that this is an initial migration file for this app<\/strong>, therefore has no previous dependencies. This is also clear from the dependencies<\/code> attribute, which is an empty list. The most important attribute is the operations<\/code> list. There\u2019s only one instruction in the list at the moment, which is responsible for creating a new database table with 4 columns (id, title, description, published_date) that will represent our Book model.<\/p>\n\n\n\nApplying migrations<\/h3>\n\n\n\n To apply the migration, you need to run migrate<\/code> command. It will execute the instructions defined in the migration file and reflect changes to the database<\/strong>.<\/p>\n\n\n\n$ python manage.py migrate\nOperations to perform:\n Apply all migrations: admin, auth, contenttypes, library, sessions\nRunning migrations:\n Applying library.0001_initial... OK<\/pre>\n\n\n\nAfter successfully applying migrations, our database just got a new table called library_book<\/code>. The default convention of naming is <app>_<model><\/code>.<\/p>\n\n\n\nChanging an existing model<\/h3>\n\n\n\n What will migrations look like if we change something inside our Book model? Let\u2019s find out. I\u2019ll remove the description field from the Book model, so the model now looks like this:<\/p>\n\n\n\n
from django.db import models\n\nclass Book(models.Model):\n title = models.CharField(max_length=255)\n published_date = models.DateTimeField()<\/pre>\n\n\n\nWe run the makemigrations<\/code> command again.<\/p>\n\n\n\n$ python manage.py makemigrations\nMigrations for 'library':\n library\\migrations\\0002_remove_book_description.py\n - Remove field description from book<\/pre>\n\n\n\nAs you can see, a new migration file was generated in the same directory as the initial one. But this one is named differently and even has a different message printed out. Let\u2019s peek into it.<\/p>\n\n\n\n
from django.db import migrations\n\nclass Migration(migrations.Migration):\n\n dependencies = [\n ('library', '0001_initial'),\n ]\n\n operations = [\n migrations.RemoveField(\n model_name='book',\n name='description',\n ),\n ]<\/pre>\n\n\n\nThere are a few major differences in comparison with the initial migration file:<\/p>\n\n\n\n
The initial=True<\/code> statement does not show up in this file, because the initial migration file, 0001_initial.py<\/code>, already exists<\/strong>.<\/li>The dependencies<\/code> list is not empty anymore. Django put a reference to the previous migration in the dependencies list <\/strong>to make it clear in what order migrations should be applied. <\/li>In the operations<\/code> list, you can notice that Django created an instruction for removing the description field from the Book model.<\/li><\/ul>\n\n\n\nAs I already mentioned, for each new migration file we need to execute the migrate command to apply the migrations<\/strong>.<\/p>\n\n\n\n$ python manage.py migrate\nOperations to perform:\n Apply all migrations: admin, auth, contenttypes, library, sessions\nRunning migrations:\n Applying library.0002_remove_book_description... OK<\/pre>\n\n\n\nHow to reverse migrations<\/h3>\n\n\n\n Another important thing to know is how to reverse migrations. In case you did a mistake, or just testing out a new migration, this will help you turn everything back as it was.<\/p>\n\n\n\n
To reverse migration in Django, look at the unique number of the migration you want to reverse to. Then type the migrate command in the following format:<\/p>\n\n\n\n
python manage.py migrate <app> <number><\/code><\/p>\n\n\n\nIn our example, let\u2019s say we want to revert a migration that removed the description from the Book model. So, we want to discard changes from 0002<\/code> and revert to 0001<\/code>. Let\u2019s do it.<\/p>\n\n\n\n$ python manage.py migrate library 0001\nOperations to perform:\n Target specific migration: 0001_initial, from library\nRunning migrations:\n Rendering model states... DONE\n Unapplying library.0002_remove_book_description... OK<\/pre>\n\n\n\nNow if we inspect the Book table in the database, we\u2019ll see that the description column is back again. <\/p>\n\n\n\n
Yet, Django didn\u2019t remove the 0002_remove_book_description.py<\/code> file from the migrations directory. So if you decide to run the migrate command again, it would migrate all the unapplied changes, including the ones from the 0002_remove_book_description.py<\/code> file.<\/p>\n\n\n\nDjango offers a useful command to track the applied migrations for each app. Running the showmigrations<\/code> command will list all the migrations, putting an x sign next to the ones that are applied<\/strong>.<\/p>\n\n\n\n$ python manage.py showmigrations\nadmin\n [X] 0001_initial\n [X] 0002_logentry_remove_auto_add\n [X] 0003_logentry_add_action_flag_choices\nauth\n [X] 0001_initial\n [X] 0002_alter_permission_name_max_length\n [X] 0003_alter_user_email_max_length\n [X] 0004_alter_user_username_opts\n [X] 0005_alter_user_last_login_null\n [X] 0006_require_contenttypes_0002\n [X] 0007_alter_validators_add_error_messages\n [X] 0008_alter_user_username_max_length\n [X] 0009_alter_user_last_name_max_length\n [X] 0010_alter_group_name_max_length\n [X] 0011_update_proxy_permissions\n [X] 0012_alter_user_first_name_max_length\ncontenttypes\n [X] 0001_initial\n [X] 0002_remove_content_type_name\nlibrary\n [X] 0001_initial\n [ ] 0002_remove_book_description\nsessions\n [X] 0001_initial<\/pre>\n\n\n\nNotice how the latest migration (0002_remove_book_description<\/code>) from the library app is unchecked. That\u2019s exactly what we wanted to achieve with reverting a migration.<\/p>\n\n\n\nWARNING <\/strong>- Not all migrations can be reverted. If you try to revert an irreversible operation, Django will raise the IrreversibleError<\/strong>.<\/pre>\n\n\n\nTips & Tricks to becoming a Django migrations ninja<\/h2>\n\n\n\n You can do powerful stuff with knowing Django migrations well. There\u2019s plenty of functionalities Django offers to define database schema, alter tables, migrate data, etc. I summarized some of the most useful points to help you master the migrations easier.<\/p>\n\n\n\n
Keep migrations clean<\/h3>\n\n\n\n The number of migration files can quickly increase if you\u2019re doing a lot of changes to models. In that case, use the squashmigrations<\/code> command to squash the chosen migrations into one file. Django will even optimize a number of operations required to be executed<\/strong> to achieve the same state.<\/p>\n\n\n\nName your migrations<\/h3>\n\n\n\n To have a more descriptive overview of generated migrations, you should name your migrations appropriately<\/strong>. By using the --name<\/code> parameter, you can give a custom name to the new migration file. For example, if you add an author field to our Book model and execute makemigrations<\/code> this way:<\/p>\n\n\n\npython manage.py makemigrations library --name add_author_field<\/code> ,<\/p>\n\n\n\nIt will create a file called 0003_add_author_field.py<\/code><\/p>\n\n\n\nBackup data before applying migrations<\/h3>\n\n\n\n If it\u2019s possible, back up your data before applying new migrations<\/strong>. Especially if complex changes are introduced with breaking changes involved. That way you can stay calm and turn everything back to normal even if it goes wrong.<\/p>\n\n\n\nExamine migration code<\/h3>\n\n\n\n Django comes with the sqlmigrate<\/code> command which enables you to see the exact SQL code generated from the migration file<\/strong>. Use it whenever you want to see how things are done under the hood.<\/p>\n\n\n\nInclude migration files in Version Control<\/h3>\n\n\n\n Unless you are just testing things locally, always include the migration files in the version control system<\/strong> (eg. Git). There are three reasons to do that:<\/p>\n\n\n\nYou should always be able to migrate the production database. For that, you\u2019ll need recorded steps of how did you even get to the current database state.<\/li> Take into consideration that for specific cases, you\u2019ll need to manually write migration code. Running the makemigrations command in a different environment will not magically generate your custom-written code.<\/li> Migrations have a huge impact on the functionalities and data. Therefore, migrations should be included in a code review as well as any other piece of code.<\/li><\/ul>\n\n\n\nConclusion<\/h2>\n\n\n\n I hope you now understand Django migrations better. In essence, it all comes down to planning and changing the models, creating migration files, and applying migrations to reflect changes to the database. Django will do all the rest dirty work for you.<\/p>\n\n\n\n
To summarize, you can migrate changes by following these 3 steps:<\/p>\n\n\n\n
Change your models<\/li> Run makemigrations<\/code> command<\/li>Run migrate<\/code> command<\/li><\/ol>\n\n\n\nThank you for reading, see you next time!<\/p>\n","protected":false},"excerpt":{"rendered":"
Whether you are new or already experienced with Django, you\u2019ve surely come across the concept called migrations. In this \u201cDjango … <\/p>\n
Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":543,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[8,9],"yoast_head":"\nDjango Migrations - Explained Through Examples - ZeroToByte<\/title>\n<meta name=\"description\" content=\"In this article, you'll get to know what Django migrations are and how to master them through real-life examples.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Django Migrations - Explained Through Examples - ZeroToByte\" \/>\n<meta property=\"og:description\" content=\"In this article, you'll get to know what Django migrations are and how to master them through real-life examples.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/\" \/>\n<meta property=\"og:site_name\" content=\"ZeroToByte\" \/>\n<meta property=\"article:published_time\" content=\"2021-12-01T23:18:06+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-12-20T15:14:05+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/zerotobyte.com\/wp-content\/uploads\/2021\/12\/django-migrations-featured-image2.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"800\" \/>\n\t<meta property=\"og:image:height\" content=\"547\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Erik Matosevic\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Erik Matosevic\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/\",\"url\":\"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/\",\"name\":\"Django Migrations - Explained Through Examples - ZeroToByte\",\"isPartOf\":{\"@id\":\"https:\/\/zerotobyte.com\/#website\"},\"datePublished\":\"2021-12-01T23:18:06+00:00\",\"dateModified\":\"2021-12-20T15:14:05+00:00\",\"author\":{\"@id\":\"https:\/\/zerotobyte.com\/#\/schema\/person\/53b9b5b312b9a3f60de94957151fa829\"},\"description\":\"In this article, you'll get to know what Django migrations are and how to master them through real-life examples.\",\"breadcrumb\":{\"@id\":\"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/zerotobyte.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Django Migrations – Explained Through Examples\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/zerotobyte.com\/#website\",\"url\":\"https:\/\/zerotobyte.com\/\",\"name\":\"ZeroToByte\",\"description\":\"Become a Better Dev!\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/zerotobyte.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/zerotobyte.com\/#\/schema\/person\/53b9b5b312b9a3f60de94957151fa829\",\"name\":\"Erik Matosevic\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/zerotobyte.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a668cef49bb3689c76ca19c86791c12d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a668cef49bb3689c76ca19c86791c12d?s=96&d=mm&r=g\",\"caption\":\"Erik Matosevic\"},\"sameAs\":[\"https:\/\/zerotobyte.com\"],\"url\":\"https:\/\/zerotobyte.com\/author\/erik\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Django Migrations - Explained Through Examples - ZeroToByte","description":"In this article, you'll get to know what Django migrations are and how to master them through real-life examples.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/","og_locale":"en_US","og_type":"article","og_title":"Django Migrations - Explained Through Examples - ZeroToByte","og_description":"In this article, you'll get to know what Django migrations are and how to master them through real-life examples.","og_url":"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/","og_site_name":"ZeroToByte","article_published_time":"2021-12-01T23:18:06+00:00","article_modified_time":"2021-12-20T15:14:05+00:00","og_image":[{"width":800,"height":547,"url":"https:\/\/zerotobyte.com\/wp-content\/uploads\/2021\/12\/django-migrations-featured-image2.webp","type":"image\/webp"}],"author":"Erik Matosevic","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Erik Matosevic","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/","url":"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/","name":"Django Migrations - Explained Through Examples - ZeroToByte","isPartOf":{"@id":"https:\/\/zerotobyte.com\/#website"},"datePublished":"2021-12-01T23:18:06+00:00","dateModified":"2021-12-20T15:14:05+00:00","author":{"@id":"https:\/\/zerotobyte.com\/#\/schema\/person\/53b9b5b312b9a3f60de94957151fa829"},"description":"In this article, you'll get to know what Django migrations are and how to master them through real-life examples.","breadcrumb":{"@id":"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/zerotobyte.com\/django-migrations-explained-through-examples\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/zerotobyte.com\/"},{"@type":"ListItem","position":2,"name":"Django Migrations – Explained Through Examples"}]},{"@type":"WebSite","@id":"https:\/\/zerotobyte.com\/#website","url":"https:\/\/zerotobyte.com\/","name":"ZeroToByte","description":"Become a Better Dev!","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/zerotobyte.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/zerotobyte.com\/#\/schema\/person\/53b9b5b312b9a3f60de94957151fa829","name":"Erik Matosevic","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/zerotobyte.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/a668cef49bb3689c76ca19c86791c12d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a668cef49bb3689c76ca19c86791c12d?s=96&d=mm&r=g","caption":"Erik Matosevic"},"sameAs":["https:\/\/zerotobyte.com"],"url":"https:\/\/zerotobyte.com\/author\/erik\/"}]}},"_links":{"self":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts\/182"}],"collection":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/comments?post=182"}],"version-history":[{"count":59,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts\/182\/revisions"}],"predecessor-version":[{"id":302,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts\/182\/revisions\/302"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/media\/543"}],"wp:attachment":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/media?parent=182"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/categories?post=182"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/tags?post=182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Database](\"https:\/\/zerotobyte.com\/wp-content\/uploads\/2021\/12\/django-migrations-01.webp\")
<\/figure>\n\n\n\n![\"Database](\"https:\/\/zerotobyte.com\/wp-content\/uploads\/2021\/12\/django-migrations-02.webp\")
<\/figure>\n\n\n\n