Re: Add RANGE with values and exclusions clauses to the Window Functions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Add RANGE with values and exclusions clauses to the Window Functions
Date
Msg-id 14068.1517266223@sss.pgh.pa.us
Whole thread Raw
In response to Re: Add RANGE with values and exclusions clauses to the Window Functions  (Oliver Ford <ojford@gmail.com>)
Responses Re: Add RANGE with values and exclusions clauses to the Window Functions
List pgsql-hackers
Oliver Ford <ojford@gmail.com> writes:
> On Monday, 29 January 2018, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I've started to go through this in some detail, and I'm wondering why
>> you invented a FRAMEOPTION_EXCLUDE_NO_OTHERS option bit rather than
>> just representing that choice as default (0).

> My guess is that it's a little like putting "ORDER BY x ASC" when ASC is
> usually default behavior - it adds some documentation, perhaps for people
> new to SQL or to make your intention more explicit. That's the only reason
> I can think of as to why the standards committee included it.

Yeah, they like to do that.  And "ORDER BY x ASC" is actually a precise
precedent, because we don't print ASC either, cf get_rule_orderby().

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: JIT compiling with LLVM v9.0
Next
From: Oliver Ford
Date:
Subject: Re: Add RANGE with values and exclusions clauses to the Window Functions