Re: postgresql function not accepting null values inselect statement

From: "Jyoti Seth" <jyotiseth2001(at)gmail(dot)com>
To: "'johnf'" <jfabiani(at)yolo(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: postgresql function not accepting null values inselect statement
Date: 2008-02-25 05:20:04
Message-ID: 002401c8776e$17698b80$463ca280$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

I have tried this, but it is showing following error:
ERROR: syntax error at or near "DISTINCT"
SQL state: 42601

Thanks,
Jyoti

-----Original Message-----
From: pgsql-sql-owner(at)postgresql(dot)org [mailto:pgsql-sql-owner(at)postgresql(dot)org]
On Behalf Of johnf
Sent: Friday, February 22, 2008 10:01 PM
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] postgresql function not accepting null values inselect
statement

On Friday 22 February 2008 01:35:47 am Bart Degryse wrote:
> Can you try this...
>
> CREATE OR REPLACE FUNCTION getfunctionaries(p_statecd integer)
> RETURNS SETOF t_functionaries AS
> $BODY$
> DECLARE
> rec t_functionaries%ROWTYPE;
> BEGIN
> FOR rec IN (
> SELECT f.functionaryid, f.category, f.description
> FROM functionaries f
> WHERE f.statecd IS NOT DISTINCT FROM p_statecd)
> LOOP
> return next rec;
> END LOOP;
> return;
> END;
> $BODY$
> LANGUAGE 'plpgsql' VOLATILE;
>
a newbie question. Could you explain why yours works? I don't understand
how
it works if p_statecd = NULL

--
John Fabiani

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Stuart Brooks 2008-02-25 06:27:17 autovacuum not freeing up unused space on 8.3.0
Previous Message Aarni Ruuhimäki 2008-02-23 21:06:28 Re: SQL standards in Mysql