mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-23 21:59:11 +00:00
Code Issues 32 Releases Wiki Activity

[1.8.x] Made assorted improvements to the Oracle documentation.

Browse Source 
Backport of 6f1b09bb5c from master
This commit is contained in:
Mariusz Felisiak
2015-09-15 22:01:31 +02:00
committed by Tim Graham
parent eb0bbb8f3a
commit a0ce708c1c
5 changed files with 28 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/intro/tutorial01.txt
View File

@@ -201,8 +201,9 @@ and creates any necessary database tables according to the database settings
in your :file:`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;`` (MySQL), or
``.schema`` (SQLite) to display the tables Django created.
database and type ``\dt`` (PostgreSQL), ``SHOW TABLES;`` (MySQL), ``.schema``
(SQLite), or ``SELECT TABLE_NAME FROM USER_TABLES;`` (Oracle) to display the
tables Django created.
.. admonition:: For the minimalists
@@ -518,7 +519,7 @@ Note the following:
* It's tailored to the database you're using, so database-specific field types
such as ``auto_increment`` (MySQL), ``serial`` (PostgreSQL), or ``integer
primary key autoincrement`` (SQLite) are handled for you automatically. Same
goes for the quoting of field names -- e.g., using double quotes or
goes for the quoting of field names -- e.g., using double quotes or
single quotes.
* The :djadmin:`sqlmigrate` command doesn't actually run the migration on your
@@ -565,9 +566,9 @@ but for now, remember the three-step guide to making model changes:
* Run :djadmin:`python manage.py migrate <migrate>` to apply those changes to
the database.
The reason that there are separate commands to make and apply migrations is
because you'll commit migrations to your version control system and ship them
with your app; they not only make your development easier, they're also
The reason that there are separate commands to make and apply migrations is
because you'll commit migrations to your version control system and ship them
with your app; they not only make your development easier, they're also
useable by other developers and in production.
Read the :doc:`django-admin documentation </ref/django-admin>` for full