Made assorted improvements to the Oracle documentation.

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

All of these privileges are included in the DBA role, which is appropriate

for use on a private developer's database.

The Oracle database backend uses the ``SYS.DBMS_LOB`` package, so your user

will require execute permissions on it. It's normally accessible to all users

by default, but in case it is not, you'll need to grant permissions like so:

The Oracle database backend uses the ``SYS.DBMS_LOB`` and ``SYS.DBMS_RANDOM``

packages, so your user will require execute permissions on it. It's normally

accessible to all users by default, but in case it is not, you'll need to grant

permissions like so:

.. code-block:: sql

    GRANT EXECUTE ON SYS.DBMS_LOB TO user;

    GRANT EXECUTE ON SYS.DBMS_RANDOM TO user;

Connecting to the database

--------------------------

* LOB columns may not be used in a ``SELECT DISTINCT`` list. This means that

  attempting to use the ``QuerySet.distinct`` method on a model that

  includes ``TextField`` columns will result in an error when run against

  Oracle. As a workaround, use the ``QuerySet.defer`` method in conjunction

  with ``distinct()`` to prevent ``TextField`` columns from being included in

  the ``SELECT DISTINCT`` list.

  includes ``TextField`` columns will result in an ``ORA-00932`` error when

  run against Oracle. As a workaround, use the ``QuerySet.defer`` method in

  conjunction with ``distinct()`` to prevent ``TextField`` columns from being

  included in the ``SELECT DISTINCT`` list.

.. _third-party-notes:

* For PostgreSQL, this runs the ``psql`` command-line client.

* For MySQL, this runs the ``mysql`` command-line client.

* For SQLite, this runs the ``sqlite3`` command-line client.

* For Oracle, this runs the ``sqlplus`` command-line client.

This command assumes the programs are on your ``PATH`` so that a simple call to

the program name (``psql``, ``mysql``, ``sqlite3``) will find the program in

the right place. There's no way to specify the location of the program

manually.

the program name (``psql``, ``mysql``, ``sqlite3``, ``sqlplus``) will find the

program in the right place. There's no way to specify the location of the

program manually.

The :djadminopt:`--database` option can be used to specify the database

onto which to open a shell.

    .. _pytz: http://pytz.sourceforge.net/

    .. _Time Zones: http://www.postgresql.org/docs/current/static/datatype-datetime.html#DATATYPE-TIMEZONES

    .. _Choosing a Time Zone File: http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch4datetime.htm#i1006667

    .. _Choosing a Time Zone File: http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch4datetime.htm#NLSPG258

    .. _mysql_tzinfo_to_sql: http://dev.mysql.com/doc/refman/5.6/en/mysql-tzinfo-to-sql.html

none

    SELECT ... WHERE title REGEXP BINARY '^(An?|The) +'; -- MySQL

    SELECT ... WHERE REGEXP_LIKE(title, '^(an?|the) +', 'c'); -- Oracle

    SELECT ... WHERE REGEXP_LIKE(title, '^(An?|The) +', 'c'); -- Oracle

    SELECT ... WHERE title ~ '^(An?|The) +'; -- PostgreSQL

* PostgreSQL users, refer to the `PostgreSQL manual`_ (section 22.3.2 in

  PostgreSQL 9) for details on creating databases with the correct encoding.

* Oracle users, refer to the `Oracle manual`_ for details on how to set

  (`section 2`_) or alter (`section 11`_) the database character set encoding.

* SQLite users, there is nothing you need to do. SQLite always uses UTF-8

  for internal encoding.

.. _MySQL manual: http://dev.mysql.com/doc/refman/5.6/en/charset-database.html

.. _PostgreSQL manual: http://www.postgresql.org/docs/current/static/multibyte.html

.. _Oracle manual: http://docs.oracle.com/cd/E11882_01/server.112/e10729/toc.htm

.. _section 2: http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch2charset.htm#NLSPG002

.. _section 11: http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#NLSPG011

All of Django's database backends automatically convert Unicode strings into

the appropriate encoding for talking to the database. They also automatically