Message-ID: <3E1D77B3.4000503@klaster.net>
Date: Thu, 09 Jan 2003 14:22:59 +0100
From: Tomasz Myrta <jasiek@klaster.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US;
	rv:1.2b) Gecko/20021016
MIME-Version: 1.0
To: Radu-Adrian Popescu <radu.popescu@aldratech.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: SQL function parse error ?
References: <008f01c2b7d0$3733fdf0$0600a8c0@rpopescu>
	<3E1D6362.80701@klaster.net>
	<00a501c2b7dc$a5c626b0$0600a8c0@rpopescu>
In-Reply-To: <008f01c2b7d0$3733fdf0$0600a8c0@rpopescu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Radu-Adrian Popescu wrote:

> I'm perfectly aware of the fact that a space solves the issue here.
>
> What I'm saying is that it is not natural nor common to take some 
> whitespace
> into
> account when parsing, since this is not bash language, nor python, as it
> shouldn't be !
> This is SQL, and people who are using PostgreSql write SQL, not
> whitespace-sensitive SQL, bash or whatever.
>
> And besides, like I have already pointed out, look at php's language 
> parser
> (behavior, not source) :
> the statement if(100>$a) is perfectly legal, as it should be.
> Is there any operator named >$ ?
>
> Anyone who has used anything from Mysql to Oracle will get quite 
> annoyed on
> this one.
>
> Hope the people in charge of the parser will get to the bottom of this...
> ... and please forgive my caustic tone.
>
> =====
> Radu-Adrian Popescu
> CSA, DBA, Developer
> Aldratech Ltd.

I think you are absolutely wrong.
It is possible in Postgresql to overload operators and if you want, you 
can create operator named ">$".

There is a lot of useful things in postgresql documentation. If you read 
it, you could find this:

 >CREATE OPERATOR defines a new operator, name. The user who defines an 
 >operator becomes its owner.
 >The operator name is a sequence of up to NAMEDATALEN-1 (31 by default) 
 >characters from the following list:
 >+ - * / < > = ~ ! @ # % ^ & | ` ? $

Regards,
Tomasz Myrta