Comments on: Return in a PL/SQL Procedure – Just one more thing Mum never told me http://mikesmithers.wordpress.com/2010/02/10/return-in-a-plsql-procedure-%e2%80%93-just-one-more-thing-mum-never-told-me/ Oracle - for when it was like that when you got there Sat, 18 May 2013 06:13:06 +0000 hourly 1 http://wordpress.com/ By: Niraj Kumar http://mikesmithers.wordpress.com/2010/02/10/return-in-a-plsql-procedure-%e2%80%93-just-one-more-thing-mum-never-told-me/#comment-22422 Tue, 11 Sep 2012 07:24:07 +0000 http://mikesmithers.wordpress.com/?p=302#comment-22422 Really good article. i also used to use raise_exception.

]]> By: Mário Barbosa http://mikesmithers.wordpress.com/2010/02/10/return-in-a-plsql-procedure-%e2%80%93-just-one-more-thing-mum-never-told-me/#comment-20482 Fri, 20 Jul 2012 10:01:27 +0000 http://mikesmithers.wordpress.com/?p=302#comment-20482 Or you could simply test for IF NOT and have the smaller block at the top and leave the “real deal” for the ELSE:

CREATE OR REPLACE PROCEDURE ins_trivial( pa_input IN VARCHAR2) AS
BEGIN

IF NOT
(ASCII( UPPER( pa_input)) NOT BETWEEN 65 AND 90) THEN
/* the smaller exceptional situation block*/
RETURN;
ELSE
/* the real deal juicy code*/
INSERT INTO trivial( letter) VALUES( pa_input);
END IF;

END;

But I did get your point. No problem with GOTOs regarding there’s only one tag at the end of the function, like we’d have with an expection approach.

]]>