From: | Michael Meskes <meskes(at)topsystem(dot)de> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Subject: | Re: [HACKERS] symbol ':' |
Date: | 1998-03-26 15:54:42 |
Message-ID: | 199803261554.QAA08202@gauss.topsystem.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
(at))
Cc: pgsql-hackers(at)postgresql(dot)org (PostgreSQL Hacker)
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Thomas G. Lockhart writes:
> It's an allowed operator symbol assigned to a little-used math
> operation. You can disallow it for embedded sql if you need to. Another
Yes, I have to.
> possibility though is to disallow it as an operator _unless_ it is
> inside parentheses. I did a similar thing in gram.y in the BETWEEN/AND
> parsing to allow the boolean "AND" operator to be used on the right side
> of BETWEEN/AND. But maybe indicator variables are allowed to show up
> inside expressions too, so this wouldn't work...
They are. And it's not only indicators. The variables begin with ':', too.
> btw, I've been thinking about changing another operator symbol, ";",
> because of the obvious parsing ambiguities with the SQL end of statement
> symbol. We could change both ":" and ";" operators for v6.4??
Good idea.
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 | Maurice Gittens | 1998-03-26 16:46:43 | Re: [HACKERS] patch for memory overrun on Linux(i386) |
Previous Message | Thomas G. Lockhart | 1998-03-26 15:18:34 | Re: [HACKERS] symbol ':' |