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.
----- Original Message -----
From: "Tomasz Myrta" <[EMAIL PROTECTED]>
To: "Radu-Adrian Popescu" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 09, 2003 1:56 PM
Subject: Re: [SQL] SQL function parse error ?
Radu-Adrian Popescu wrote:
>
> Take the following for example:
> create or replace function testfunc1(int) returns setof test as
> '
> select * from test where age>$1;
> ' ^^^^^^
> language sql;
I didn't find it in documentation, but sql functions are like bash (you
forgot about space character):
create or replace function testfunc1(int) returns setof test as
'
select * from test where age > $1;
'
works fine.
Postgresql thinks that >$ is an operator instead of >
Tomasz Myrta
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
