From 46852956da902e15edc266aaf216ec55e0902a79 Mon Sep 17 00:00:00 2001 From: Andreu Vallbona Date: Sat, 8 Jun 2024 15:24:41 +0200 Subject: [PATCH] code review fixes --- docs/intro/tutorial02.txt | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/intro/tutorial02.txt b/docs/intro/tutorial02.txt index b21e625c32..402b6eee37 100644 --- a/docs/intro/tutorial02.txt +++ b/docs/intro/tutorial02.txt @@ -255,13 +255,6 @@ Don't worry, you're not expected to read them every time Django makes one, but they're designed to be human-editable in case you want to manually tweak how Django changes things. -There's a command that will run the migrations for you and manage your database -schema automatically - that's called :djadmin:`migrate`. - -If you're interested, you can also run -:djadmin:`python manage.py check `; this checks for any problems in -your project without making migrations or touching the database. - Now, run :djadmin:`migrate` again to create those model tables in your database: .. console:: @@ -273,6 +266,10 @@ Now, run :djadmin:`migrate` again to create those model tables in your database: Rendering model states... DONE Applying polls.0001_initial... OK +If you're interested, you can also run +:djadmin:`python manage.py check `; this checks for any problems in +your project without making migrations or touching the database. + The :djadmin:`migrate` command takes all the migrations that haven't been applied (Django tracks which ones are applied using a special table in your database called ``django_migrations``) and runs them against your database -