From: Dino Maric <dinom@hey.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Confusion about the range types
Date: Sun, 08 Jan 2023 11:13:57 +0100
Message-ID: <276a2c3825d677698e392f92d45893d1dc93d797@hey.com> (raw)
In-Reply-To: <3452152.1673107986@sss.pgh.pa.us>
Thanks Tom, I understand.
But still it does feel a bit strange that value I'm storing is different
when presenting.
For example I want to use range in healthcare app and value user stores
it must be the same when presenting.
So in that case it is [7-8] and [7-9) are not the same thing :)
On January 7, 2023, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dino Maric <dinom@hey.com> writes:
> > When I insert range like this:
> > INSERT INTO public.tests
> > VALUES (int4range(7,8,'[]'))
> > After when querying table my return value for this column is not
> [7,8]
> > but it is [7,9).
> > I found this behaviour confusing, because I want to insert 7-8
> ranges
> > (including upper value) and then present that range to a user.
>
> This is the effect of canonicalization, as explained here:
>
> https://www.postgresql.org/docs/current/rangetypes.html#RANGETYPES-
> DISCRETE
>
> If you don't like it you can make a range type with a different
> canonicalization function, or no such function, but that might
> have odd effects on the behavior of range comparison operators.
>
> regards, tom lane
--
Sent with HEY <https://hey.com/sent; — Email as it should be
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: dinom@hey.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: Confusion about the range types
In-Reply-To: <276a2c3825d677698e392f92d45893d1dc93d797@hey.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox