diff options
| author | Mariusz Felisiak <mariusz.felisiak@mga.com.pl> | 2015-09-15 22:01:31 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-09-18 09:50:35 -0400 |
| commit | a0ce708c1cfa29c13d7334bb27d9c91f570307e8 (patch) | |
| tree | b8bdada4b1eb886dac891040b9b2e4f69efed44d /docs/intro | |
| parent | eb0bbb8f3a31eb46eb97771cd9c1eccaf01be119 (diff) | |
[1.8.x] Made assorted improvements to the Oracle documentation.
Backport of 6f1b09bb5c1bafe4633514cbff37f9a7ed7a63ae from master
Diffstat (limited to 'docs/intro')
| -rw-r--r-- | docs/intro/tutorial01.txt | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt index ac0e4fff26..2c45246566 100644 --- a/docs/intro/tutorial01.txt +++ b/docs/intro/tutorial01.txt @@ -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 |