Re: Should we still require RETURN in plpgsql? - Mailing list pgsql-hackers

From Terry Yapt
Subject Re: Should we still require RETURN in plpgsql?
Date
Msg-id udg451tcop8o779h9vmi3l9gdgu7tuvpij@4ax.com
Whole thread Raw
In response to Should we still require RETURN in plpgsql?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hello...

On Tue, 05 Apr 2005 02:28:23 -0400, tgl@sss.pgh.pa.us (Tom Lane)
wrote:
>
>How does Oracle's PL/SQL handle this?

On ORACLE a FUNCTION MUST return a value.  If the FUNCTION doesn't
return a value Oracle give a 'hint' on FUNCTION compilation and error
on SELECT function invocation:  ORA-06503.

When we don't want to return any result on ORACLE we must use
PROCEDURE statement instead of FUNCTION.

Example:

========
SQL> CREATE OR REPLACE FUNCTION F_test RETURN NUMBER IS 2      BEGIN 3        NULL; 4      END F_TEST; 5  /

Function created.

SQL> SELECT F_TEST FROM DUAL;
SELECT TUZSA.F_TEST FROM DUAL      *
ERROR at line 1:
ORA-06503: PL/SQL: Function returned without value
ORA-06512: at "F_TEST", line 3


SQL> 
========

Greetings.



pgsql-hackers by date:

Previous
From: "Mario Reis"
Date:
Subject: Raise Exception
Next
From: Master of the beasts
Date:
Subject: Catching DDL events (or equivalent functionality)