Re: SQL function parse error ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, Radu-Adrian Popescu <radu(dot)popescu(at)aldratech(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: SQL function parse error ?
Date: 2003-01-09 17:17:15
Message-ID: 5570.1042132635@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> Although the rules could be similar to those for + and - at the end of
> operator strings (no $ at the end of an operator unless it contains
> characters not normally in SQL92 operators). I'm not sure that
> behavior is sensible either, but if someone wanted to
> do it for their own installation it's about a 2 line patch.

It could be done that way. But given that "$" already has one weird
special case in the operator name rules (ie, it can't be the only
character of an operator name), I feel that we'd be making things overly
complicated.

The proposal back in Aug 2001 was to remove "$" from the set of operator
name characters altogether (which would allow us to use it in
identifiers instead, improving Oracle compatibility). I originally
objected to that idea on backwards-compatibility grounds, but I'm
leaning more and more to the view that it's the right thing to do.

I've re-opened the thread on pgsql-hackers about this, and we'll see
whether any consensus emerges this time.

regards, tom lane

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Radu-Adrian Popescu 2003-01-09 17:37:03 Re: SQL function parse error ?
Previous Message Stephan Szabo 2003-01-09 17:00:31 Re: SQL function parse error ?