Fixed #13245: Explained Oracle's behavior w.r.t db_table

and how to prevent table-name truncation

Thanks russellm & timo for discussion, and timo for review.

1 files changed, 12 insertions, 0 deletions

diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt
index b3d6533f9f..22ced5fe7d 100644
--- a/docs/ref/models/options.txt
+++ b/docs/ref/models/options.txt
@@ -72,6 +72,18 @@ Django quotes column and table names behind the scenes.
     the table name via ``db_table``, particularly if you are using the MySQL
     backend. See the :ref:`MySQL notes <mysql-notes>` for more details.
 
+.. admonition:: Table name quoting for Oracle
+
+   In order to to meet the 30-char limitation Oracle has on table names,
+   and match the usual conventions for Oracle databases, Django may shorten
+   table names and turn them all-uppercase. To prevent such transformations,
+   use a quoted name as the value for ``db_table``::
+
+       db_table = '"name_left_in_lowercase"'
+
+   Such quoted names can also be used with Django's other supported database 
+   backends; except for Oracle, however, the quotes have no effect. See the
+   :ref:`Oracle notes <oracle-notes>` for more details.
 
 ``db_tablespace``
 -----------------