| From: | Michael Meskes <meskes(at)topsystem(dot)de> |
|---|---|
| To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
| Cc: | pgsql-hackers(at)postgresql(dot)org (PostgreSQL Hacker) |
| Subject: | Re: [HACKERS] shift/reduce problem with ecpg |
| Date: | 1998-04-21 10:34:25 |
| Message-ID: | 199804211034.MAA11806@gauss.topsystem.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas G. Lockhart writes:
> Yes. If you really want to allow zero, one, or two colons, and only that
> number, then you can explicitly define those cases and separate them out
> from the a_expr syntax except as an argument. Look in gram.y for
> "b_expr" which accomplishes a similar thing for the BETWEEN operator.
> For that case, the AND usage was ambiguous since it can be used for
> boolean expressions and is also used with the BETWEEN operator.
Thanks Thomas. I've created a c_expr to be used in opt_indirection. Since
indicators don't make sense in this position only variables may be entered
here.
Michael
--
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Sysoev | 1998-04-21 10:45:15 | subselect and optimizer |
| Previous Message | Patrice Hédé | 1998-04-21 10:33:33 | Re: [DOCS] FAQ organization |