Skip site navigation (1) Skip section navigation (2)

Re: Return void error in PG 8.1.0

From: "Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Return void error in PG 8.1.0
Date: 2005-12-09 20:27:58
Message-ID: F7638DABBEBB4A4CB70616DE2B19E6B86509E4@COENGEXCMB01.cable.comcast.com (view raw or flat)
Thread:
Lists: pgsql-novice
Thanks, I tested that and "returns void" does work properly with just
"return". 

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
Sent: Friday, December 09, 2005 1:22 PM
To: Walker, Jed S
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Return void error in PG 8.1.0 

"Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com> writes:
> We are testing our system using PG 8.1.0 instead of 8.0.4. When I 
> recreated functions I discovered that the ones that have "returns
void"
> and do return void all failed with the following error (when creating
> them):

> ERROR:  RETURN cannot have a parameter in function returning void at 
> or near "void" at character 357

> Is this a known issue or change to PG? Is there a way to still return 
> void in 8.1.0?

"return void" was never correct; the correct and documented thing is
just "return"; but older versions of plpgsql were laxer about
complaining about junk in a RETURN that should have no parameter.

			regards, tom lane

pgsql-novice by date

Next:From: operationsengineer1Date: 2005-12-09 21:54:13
Subject: Bind Variables and Quoting / Dequoting Input
Previous:From: Tom LaneDate: 2005-12-09 20:21:51
Subject: Re: Return void error in PG 8.1.0

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group