mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-04-22 00:04:43 +00:00
Code Issues 32 Releases Wiki Activity

[5.1.x] Fixed #36078 -- Doc'd that Postgres normalizes a range field with no points to empty.

Browse Source 
Co-authored-by: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com>

Backport of 611e7bc3a0633a35ae3430e359c646e02fa3801d from main.
This commit is contained in:
Clifford Gama 2025-01-16 14:05:50 +02:00 committed by Sarah Boyce
parent 71558701df
commit d05cf7c35f
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -517,6 +517,15 @@ excluded, that is ``[)`` (see the PostgreSQL documentation for details about
fields (:class:`.DateTimeRangeField` and :class:`.DecimalRangeField`) by using
the ``default_bounds`` argument.
.. admonition:: PostgreSQL normalizes a range with no points to the empty range
A range with equal values specified for an included lower bound and an
excluded upper bound, such as ``Range(datetime.date(2005, 6, 21),
datetime.date(2005, 6, 21))`` or ``[4, 4)``, has no points. PostgreSQL will
normalize the value to empty when saving to the database, and the original
bound values will be lost. See the `PostgreSQL documentation for details
<https://www.postgresql.org/docs/current/rangetypes.html#RANGETYPES-IO>`_.
``IntegerRangeField``
---------------------