Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Start with [ , end with )
From: "Jonathan S. Katz" <jkatz@postgresql.org>
In-Reply-To: 
 <CAM2FmMqvNbf_-hRJWLgtrxSf0kdEoRdwfCFVxx2gN2Kd=3+g6A@mail.gmail.com>
Date: Mon, 23 Apr 2018 22:09:56 -0700
Cc: yonatanhak@gmail.com,
 pgsql-docs@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <73E74C0B-CE76-4E7F-BBE6-545EFC9582D1@postgresql.org>
References: <152448843926.19802.14056302746131184432@wrigleys.postgresql.org>
 <CAM2FmMqvNbf_-hRJWLgtrxSf0kdEoRdwfCFVxx2gN2Kd=3+g6A@mail.gmail.com>
To: Mike Toews <mwtoews@gmail.com>
Precedence: bulk


> On Apr 23, 2018, at 8:37 PM, Mike Toews <mwtoews@gmail.com> wrote:
>=20
> On 24 April 2018 at 01:00, PG Doc comments form =
<noreply@postgresql.org> wrote:
>> 8.17.2. Examples
>>=20
>> CREATE TABLE reservation (room int, during tsrange);
>> INSERT INTO reservation VALUES
>>    (1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
>>               ^                                                       =
  ^
>> While not an Error, still...
>=20
> See 8.17.3. Inclusive and Exclusive Bounds
>=20
> This is an example with an inclusive lower bound "[" and an exclusive
> upper bound ")=E2=80=9D.

When dealing with date/time ranges, it=E2=80=99s a very common use case =
to have
an inclusive lower-bound and exclusive upper-bound, especially when
dealing with scheduling.

Jonathan