From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Shawn Tayler <stayler(at)washoecounty(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2788: Create Function operator Broken? |
Date: | 2006-11-28 05:08:37 |
Message-ID: | 20061127210109.Q12772@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, 27 Nov 2006, Shawn Tayler wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2788
> Logged by: Shawn Tayler
> Email address: stayler(at)washoecounty(dot)us
> PostgreSQL version: 8.1.5
> Operating system: Linux 2.6.17
> Description: Create Function operator Broken?
> Details:
>
> I have been through the online DOC's the FAQ and can find nothing wrong with
> it. So I am thinking its a bug.
>
> CREATE FUNCTION default_status() returns null AS
Do you mean returns void? I believe the issue is that returns null starts
the "returns null on null input" function attribute.
> 'BEGIN
> update status set wc to false, np to false, elk to false, sp1 to false,
> sp2 to false, wc_rep to false, np_rep to false, elk_rep to false, sp1_rep to
> false,
> sp2_rep to false;
> END;'
> language 'sql';
The above body isn't valid for an sql body as well.
Sql functions won't have a begin or end, and I don't think those "to"s
will be valid either.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-11-28 08:58:41 | Re: BUG #2786: PGADMIN 1.6 |
Previous Message | Tom Lane | 2006-11-28 04:36:02 | Re: BUG #2781: database dump/restore problems |