From 611e7bc3a0633a35ae3430e359c646e02fa3801d Mon Sep 17 00:00:00 2001 From: Clifford Gama Date: Thu, 16 Jan 2025 14:05:50 +0200 Subject: [PATCH] Fixed #36078 -- Doc'd that Postgres normalizes a range field with no points to empty. Co-authored-by: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> --- docs/ref/contrib/postgres/fields.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/ref/contrib/postgres/fields.txt b/docs/ref/contrib/postgres/fields.txt index ec767b50e9..65bff7f9e6 100644 --- a/docs/ref/contrib/postgres/fields.txt +++ b/docs/ref/contrib/postgres/fields.txt @@ -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 + `_. + ``IntegerRangeField`` ---------------------