Re: Syntax conflicts in frame clause - Mailing list pgsql-hackers

From Hitoshi Harada
Subject Re: Syntax conflicts in frame clause
Date
Msg-id e08cc0400911241703u4bf53ek1c3910605a3d8778@mail.gmail.com
Whole thread Raw
In response to Re: Syntax conflicts in frame clause  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2009/11/25 Tom Lane <tgl@sss.pgh.pa.us>:
> Hitoshi Harada <umi.tanuki@gmail.com> writes:
>> Rewriting my frame support types patch to allow any expression in
>> PRECEDING/FOLLOWING clause, I found the syntax below in PG conflicts:
>
> Yeah, we ran into that in the original WINDOW patch IIRC, and found some
> solution to it that got taken out again when the functionality was cut
> down for 8.4.  You might want to look back to see what that looked like;
> I think we avoided reserving BETWEEN at the cost of making the
> productions a bit more redundant.

Oops, I've forgot that :(

http://archives.postgresql.org/message-id/6363.1229890896@sss.pgh.pa.us

At the time you put BETWEEN as reserved_keyword, but my trial showed
col_name_keyword can also be a candidate.

Regards,

--
Hitoshi Harada


pgsql-hackers by date:

Previous
From: Roger Leigh
Date:
Subject: Re: garbage in psql -l
Next
From: Simon Riggs
Date:
Subject: Re: Hot standby and removing VACUUM FULL