This is a discussion on Re: Return void error in PG 8.1.0 within the pgsql Novice forums, part of the PostgreSQL category; --> Thanks, I tested that and "returns void" does work properly with just "return". -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Thanks, I tested that and "returns void" does work properly with just "return". -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Friday, December 09, 2005 1:22 PM To: Walker, Jed S Cc: pgsql-novice@postgresql.org Subject: Re: [NOVICE] Return void error in PG 8.1.0 "Walker, Jed S" <Jed_Walker@cable.comcast.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 ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |