Subject: Re: SQL function parse error ?
From: Robert Treat <xzilla@users.sourceforge.net>
To: Radu-Adrian Popescu <radu.popescu@aldratech.com>
Cc: Achilleus Mantzios <achill@matrix.gatewaynet.com>,
	Tom Lane <tgl@sss.pgh.pa.us>, pgsql-sql@postgresql.org
In-Reply-To: <006301c2b7fc$41e58e40$0600a8c0@rpopescu>
References: <Pine.LNX.4.44.0301091723290.22067-100000@matrix.gatewaynet.com>
	<777.1042127826@sss.pgh.pa.us>
	<006301c2b7fc$41e58e40$0600a8c0@rpopescu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 09 Jan 2003 15:44:03 -0500
Message-Id: <1042145043.2007.31.camel@camel>
Mime-Version: 1.0

On Thu, 2003-01-09 at 11:29, Radu-Adrian Popescu wrote:
> What i'm saying is that i know that some of my colleagues, nice guys for
> that matter, and good programmers, will come screaming
> to me "what's with the b.s. error ?!?", and when i'll tell them that the sql
> parser belives that's an inexisting operator, they'll start
> cursing at it, just like i did.
>

Does oracle or mysql or whichever db you like allow the use of $ in user
defined operators?  If so, how do they know the difference?

 For what it's worth, some policy should be enforced, because it shouldn't
> matter how many spaces you put between the operator
> and the operand, as writing SELECT * is the same as SELECT
> *.
> I rest my case.
> 

Thats an invalid comparison.  The problem is not that foo >         $1
doesn't work, as your example put forth. The problem is that foo>$1
doesn't work, which by comparison would be SELECT* which would also not
work.

Robert Treat