public inbox for [email protected]  
help / color / mirror / Atom feed
From: Daniel Fredouille <[email protected]>
To: Laurenz Albe <[email protected]>
Cc: [email protected]
Subject: Re: unnest multirange, returned order
Date: Wed, 4 Oct 2023 20:04:41 -0400
Message-ID: <CAEpV6kVJc7a3i86G5ifzn9hONxpbgvbP1g_xqidW3fMhTQ54yA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <169627213477.3727338.17653654241633692682@wrigleys.postgresql.org>
	<[email protected]>
	<CAEpV6kX9PJAuQ_=5c7ZxCSASu76hkvGfVvwU6WkHTRXzApknfQ@mail.gmail.com>
	<[email protected]>

Trying a suggestion then:

"""

unnest ( anymultirange ) → setof anyrange

Expands a multirange into a set of ranges. The ranges are read out in
storage order (ascending) and therefore cannot be relied upon.

unnest('{[1,2), [3,4)}'::int4multirange) →

 [1,2)
 [3,4)

"""
Daniel

Le mer. 4 oct. 2023 à 03:20, Laurenz Albe <[email protected]> a
écrit :

> On Tue, 2023-10-03 at 20:40 -0400, Daniel Fredouille wrote:
> > > I'd say that the storag order is the order in which PostgreSQL stores
> > > multiranges internally:
> >
> > Right, I believe that you are right but then this information is not
> useful for the developer.
> > If storage order is always ascending by range order then let's make it
> clear,
> > if order cannot be counted upon as it may evolve from postgres version
> to version,
> > then let's make it clear as well. WDYT ?
>
> I personally think that it is clear as it is written now.
>
> If you have a good suggestion for an improvement, you could send it;
> perhaps someone will pick it up.
>
> Yours,
> Laurenz Albe
>


view thread (6+ messages)

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: unnest multirange, returned order
  In-Reply-To: <CAEpV6kVJc7a3i86G5ifzn9hONxpbgvbP1g_xqidW3fMhTQ54yA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox