mirror of
https://github.com/django/django.git
synced 2025-06-05 03:29:12 +00:00
code review fixes
This commit is contained in:
parent
fdfc8b03ac
commit
46852956da
@ -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 <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 <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 -
|
||||
|
Loading…
x
Reference in New Issue
Block a user