summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorAlexander Sosnovskiy <alecs.box@gmail.com>2015-11-13 10:56:10 +0300
committerTim Graham <timograham@gmail.com>2015-12-04 07:55:41 -0500
commitb61eab18f71f3afb36b3e8cb208a145046b3d8f6 (patch)
tree692a8dc30a5cad2ba66cb2d33b754390a136b210 /docs/ref
parent0e7d59df3ed6988cd5a45e26414c013ad40c7402 (diff)
Fixed #13774 -- Added models.Field.rel_db_type().
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/models/fields.txt13
1 files changed, 12 insertions, 1 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index e1b80d5fea..033ae14778 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -1701,7 +1701,8 @@ Field API reference
where the arguments are interpolated from the field's ``__dict__``.
- To map a ``Field`` to a database-specific type, Django exposes two methods:
+ To map a ``Field`` to a database-specific type, Django exposes several
+ methods:
.. method:: get_internal_type()
@@ -1717,6 +1718,16 @@ Field API reference
See :ref:`custom-database-types` for usage in custom fields.
+ .. method:: rel_db_type(connection)
+
+ .. versionadded:: 1.10
+
+ Returns the database column data type for fields such as ``ForeignKey``
+ and ``OneToOneField`` that point to the :class:`Field`, taking
+ into account the ``connection``.
+
+ See :ref:`custom-database-types` for usage in custom fields.
+
There are three main situations where Django needs to interact with the
database backend and fields: