From: Jonathan S. Katz <jkatz@postgresql.org>
To: Mike Toews <mwtoews@gmail.com>
Cc: yonatanhak@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Start with [ , end with )
Date: Mon, 23 Apr 2018 22:09:56 -0700
Message-ID: <73E74C0B-CE76-4E7F-BBE6-545EFC9582D1@postgresql.org> (raw)
In-Reply-To: <CAM2FmMqvNbf_-hRJWLgtrxSf0kdEoRdwfCFVxx2gN2Kd=3+g6A@mail.gmail.com>
References: <152448843926.19802.14056302746131184432@wrigleys.postgresql.org>
<CAM2FmMqvNbf_-hRJWLgtrxSf0kdEoRdwfCFVxx2gN2Kd=3+g6A@mail.gmail.com>
> On Apr 23, 2018, at 8:37 PM, Mike Toews <mwtoews@gmail.com> wrote:
>
> On 24 April 2018 at 01:00, PG Doc comments form <noreply@postgresql.org> wrote:
>> 8.17.2. Examples
>>
>> 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...
>
> See 8.17.3. Inclusive and Exclusive Bounds
>
> This is an example with an inclusive lower bound "[" and an exclusive
> upper bound ")”.
When dealing with date/time ranges, it’s a very common use case to have
an inclusive lower-bound and exclusive upper-bound, especially when
dealing with scheduling.
Jonathan
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-docs@postgresql.org
Cc: jkatz@postgresql.org, mwtoews@gmail.com, yonatanhak@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Start with [ , end with )
In-Reply-To: <73E74C0B-CE76-4E7F-BBE6-545EFC9582D1@postgresql.org>
* 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