original)
The migrate command looks at the INSTALLED_APPS setting and creates any
necessary database tables according to the database settings in your
mysite/settings.py file and the database migrations shipped with the app
(we'll cover those later). You'll see a message for each migration it
applies. If you're interested, run the command-line client for your
database and type \dt (PostgreSQL), SHOW TABLES; (MariaDB, MySQL), .schema
(SQLite), or SELECT TABLE_NAME FROM USER_TABLES; (Oracle) to display the
tables Django created.
Korean)
migration 커맨드는 INSTALLED_APPS를 확인한 후에 mysite/settings.py 파일의
데이터베이스 설정을 이용해서 필요한 Database Table을 생성합니다. 그리고
Database migration을 통해 생성된 결과물은 앱과 함께 제공됩니다(추후 살펴
볼 예정). 위의 커맨드를 통해 Database migration이 적용되는 메시지를 확인할
수 있습니다. 또한, 설정한 Database client을 실행하고 다음의 커맨드를 이용
해서 Django가 생성한 Table들을 확인할 수 있습니다: \dt (PostgreSQL), SHOW
TABLES; (MariaDB, MySQL), .schema (SQLite), or SELECT TABLE_NAME FROM
USER_TABLES; (Oracle)
--
Ticket URL: <https://code.djangoproject.com/ticket/31585>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => invalid
Comment:
Thanks for the report, however, translations are handled at
[https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations.
Transifex] and not in this tracker.
--
Ticket URL: <https://code.djangoproject.com/ticket/31585#comment:1>