On Mon, Jul 3, 2017 at 2:06 PM, Dean Rasheed <dean.a.rash...@gmail.com> wrote: > On 3 July 2017 at 06:00, Amit Langote <langote_amit...@lab.ntt.co.jp> wrote: >> On 2017/07/03 2:15, Dean Rasheed wrote: >>> My first thought was UNBOUNDED ABOVE/BELOW, because that matches the >>> terminology already in use of upper and lower bounds. >> >> I was starting to like the Ashutosh's suggested UNBOUNDED MIN/MAX syntax, >> but could you clarify your comment that ABOVE/BELOW is the terminology >> already in use of upper and lower bounds? I couldn't find ABOVE/BELOW in >> our existing syntax anywhere that uses the upper/lower bound notion, so >> was confused a little bit. >> > > I just meant that the words "above" and "below" more closely match the > already-used terms "upper" and "lower" for the bounds, so that > terminology seemed more consistent, e.g. "UNBOUNDED ABOVE" => no upper > bound. > > >> Also, I assume UNBOUNDED ABOVE signifies positive infinity and vice versa. >> > > Right. > > I'm not particularly wedded to that terminology. I always find naming > things hard, so if anyone can think of anything better, let's hear it.
Yet another option: UNBOUNDED UPPER/LOWER. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers