On Sun, 14 Jan 2001, Michael Richards wrote:
> I do not understand how this can possibly be correct unless NULL is
> not permitted in a function.
>
> In one case, I've got:
> WHERE value= $1
> Which is called with NULL and therefore should be:
> WHERE value= NULL
> This fails.
Right, but value
I do not understand how this can possibly be correct unless NULL is
not permitted in a function.
In one case, I've got:
WHERE value= $1
Which is called with NULL and therefore should be:
WHERE value= NULL
This fails.
The other case which is logically equivalent I've got:
WHERE value= $1 OR ($1=
On Sun, 14 Jan 2001, Michael Richards wrote:
> Hi.
>
> I'm using 7.0.3 and I've found a bug:
>
> create table test(value int4);
> create function testfunc(int4)
> RETURNS bool AS
> 'SELECT count(*)>0 AS RESULT FROM test where value= $1'
> language 'SQL';
>
> So I want this
Hi.
I'm using 7.0.3 and I've found a bug:
create table test(value int4);
create function testfunc(int4)
RETURNS bool AS
'SELECT count(*)>0 AS RESULT FROM test where value= $1'
language 'SQL';
So I want this function to return true when it finds the specified
value in the t
