Re: Precedence of NOT LIKE, NOT BETWEEN, etc

From: Greg Stark <stark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Precedence of NOT LIKE, NOT BETWEEN, etc
Date: 2015-04-08 17:11:16
Message-ID: CAM-w4HMFfNWFTN7SPi3RxTg=0i_b8Thtfm2W7=qhzS6Um=nX5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 24, 2015 at 5:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Also, it strikes me that we could significantly reduce, maybe even fully
> eliminate, the funny behaviors around the existing base_yylex()
> substitutions if we made them use the same idea, ie replace the leading
> token with something special but keep the second token's separate
> identity. Unless somebody sees a hole in this idea, I'll probably go
> do that and then come back to the precedence issues.

IIRC that's exactly what the earlier patch for this did.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-04-08 17:14:38 Re: Precedence of NOT LIKE, NOT BETWEEN, etc
Previous Message Tom Lane 2015-04-08 16:37:29 Re: Support UPDATE table SET(*)=...