innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #31577 -- Clarified docs about bounds of RangeFields.

This commit is contained in:
xncbf 2020-05-17 16:54:26 +09:00 committed by Mariusz Felisiak
parent 3b1cb78063
commit 4029bcd6b2
2 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
AUTHORS
View File

@ -509,6 +509,7 @@ answer newbie questions, and generally made Django that much better:
Kevin McConnell <kevin.mcconnell@gmail.com> Kevin McConnell <kevin.mcconnell@gmail.com>
Kieran Holland <http://www.kieranholland.com> Kieran Holland <http://www.kieranholland.com>
kilian <kilian.cavalotti@lip6.fr> kilian <kilian.cavalotti@lip6.fr>
Kim Joon Hwan 김준환 <xncbf12@gmail.com>
Klaas van Schelven <klaas@vanschelven.com> Klaas van Schelven <klaas@vanschelven.com>
knox <christobzr@gmail.com> knox <christobzr@gmail.com>
konrad@gwu.edu konrad@gwu.edu

11
docs/ref/contrib/postgres/fields.txt
View File

@ -538,7 +538,10 @@ suitable for.
All of the range fields translate to :ref:`psycopg2 Range objects All of the range fields translate to :ref:`psycopg2 Range objects
<psycopg2:adapt-range>` in Python, but also accept tuples as input if no bounds <psycopg2:adapt-range>` in Python, but also accept tuples as input if no bounds
information is necessary. The default is lower bound included, upper bound information is necessary. The default is lower bound included, upper bound
excluded; that is, ``[)``. excluded, that is ``[)`` (see the PostgreSQL documentation for details about
`different bounds`_).
.. _different bounds: https://www.postgresql.org/docs/current/rangetypes.html#RANGETYPES-IO
``IntegerRangeField`` ``IntegerRangeField``
--------------------- ---------------------
@ -552,7 +555,7 @@ excluded; that is, ``[)``.
Regardless of the bounds specified when saving the data, PostgreSQL always Regardless of the bounds specified when saving the data, PostgreSQL always
returns a range in a canonical form that includes the lower bound and returns a range in a canonical form that includes the lower bound and
excludes the upper bound; that is ``[)``. excludes the upper bound, that is ``[)``.
``BigIntegerRangeField`` ``BigIntegerRangeField``
------------------------ ------------------------
@ -566,7 +569,7 @@ excluded; that is, ``[)``.
Regardless of the bounds specified when saving the data, PostgreSQL always Regardless of the bounds specified when saving the data, PostgreSQL always
returns a range in a canonical form that includes the lower bound and returns a range in a canonical form that includes the lower bound and
excludes the upper bound; that is ``[)``. excludes the upper bound, that is ``[)``.
``DecimalRangeField`` ``DecimalRangeField``
--------------------- ---------------------
@ -599,7 +602,7 @@ excluded; that is, ``[)``.
Regardless of the bounds specified when saving the data, PostgreSQL always Regardless of the bounds specified when saving the data, PostgreSQL always
returns a range in a canonical form that includes the lower bound and returns a range in a canonical form that includes the lower bound and
excludes the upper bound; that is ``[)``. excludes the upper bound, that is ``[)``.
Querying Range Fields Querying Range Fields
--------------------- ---------------------