Horton

Re: Row pattern recognition

David G. Johnston <david.g.johnston@gmail.com>

View thread
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Vik Fearing <vik@postgresfriends.org>
Cc: Tatsuo Ishii <ishii@postgresql.org>, jacob.champion@enterprisedb.com, pgsql-hackers@postgresql.org, er@xs4all.nl, peter@eisentraut.org
Date: 2024-10-22T14:19:41Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add temporal FOREIGN KEY contraints

  2. Remove obsolete executor cleanup code

On Tue, Oct 22, 2024 at 6:12 AM Vik Fearing <vik@postgresfriends.org> wrote:

>
> On 22/10/2024 12:19, Tatsuo Ishii wrote:
>
> Acording to ISO/IEC 9075-2:2016 "4.21.2 Row pattern navigation operations",
>
>   <row pattern navigation operation> evaluates a <value expression> VE
>   in a row NR, which may be different than current row CR.
>
> From this I think PREV(col + 1) should be interpreted as:
>
> 1. go to the previous row.
> 2. evaluate "col + 1" at the current row (that was previous row).
> 3. return the result.
>
> If my understanding is correct, prev(price + 1) has the same meaning
> as prev(price) + 1.
>
>
>
> This is how I read the specification also.
>
>
>
That makes sense.  Definitely much nicer to only have to write PREV once if
the expression you are evaluating involves multiple columns.  And is also
consistent with window function "value" behavior.

Thanks!

David J.