| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] subquery syntax broken |
| Date: | 1998-02-03 08:34:58 |
| Message-ID: | 34D6D6B2.B44F2C33@sable.krasnoyarsk.su |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas G. Lockhart wrote:
>
> > I believe it has to do with the fact that '=' has right precedence.
> > Thomas, can you comment. Maybe we need to %right 'Op' at that point so
> > it doesn't shift too early?
>
> No, the single-character operators each need their own code in the parser.
> Check near line 2980 in the parser for examples from the "a_expr" syntax. You
> just need to replicate the subselect "Op" definition blocks and substitute
> each of '=', '<', and '>' in the copies. The existing "Op" code handles the
Don't forget about ALL/ANY modifiers, too...
> multi-character operators such as '<=' and '>='...
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL | 1998-02-03 08:53:28 | Re: [HACKERS] Speed boost + Others |
| Previous Message | Thomas G. Lockhart | 1998-02-03 08:18:37 | Re: [HACKERS] subquery syntax broken |