pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jie Liang <jliang@ipinc.com>
To: Jeff Eckermann <jeckermann@verio.net>
Cc: 'pgsql-sql@postgresql.org' <pgsql-sql@postgresql.org>
Subject: Re: Use of RETURN in pl/pgsql function
Date: Wed, 7 Feb 2001 14:32:39 -0800 (PST)
Message-ID: <Pine.BSF.4.10.10102071307020.17745-100000@tidal.ipinc.com> (raw)
In-Reply-To: <08CD1781F85AD4118E0800A0C9B8580B0948FD@NEZU>


You may try like:

if block
end if;
return somefakething;

no matter this return can be reached or not.
then compile will be no problem.

Jie LIANG

Internet Products Inc.

10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873

jliang@ipinc.com
www.ipinc.com

On Wed, 7 Feb 2001, Jeff Eckermann wrote:

> My script is below.
> 
> I thought (based on recent posts) that this use of RETURN is allowed, but
> when trying an insert to report_table, I get the following error:
> 
> ERROR:  control reaches end of trigger procedure without RETURN
> 
> I have solved several problems in getting to this point, but have now run
> out of ideas.  I would appreciate any pointers.
> 
> jeffe@kiyoko=> uname -a
> FreeBSD kiyoko.la.verio.net 4.0-STABLE FreeBSD 4.0-STABLE #0: Thu Apr 27
> 10:44:07 CDT 2000
> jeffe@kiyoko=> psql -V
> psql (PostgreSQL) 7.0.0
> 
> Script:
> 
> drop function mrr();
> 
> create function mrr() returns opaque as '
> 
> begin
> 
> if NEW.billing_frequency = ''Monthly''          -- That's doubled single
> quotes (and below as well)
> 
> then
> 
>         return NEW;
> 
> else
> 
>         if NEW.billing_frequency = ''Yearly''
> 
>         then
> 
>                 NEW.rate := NEW.rate/12;
>  
>                 NEW.rate_override := NEW.rate_override/12;
> 
>                 return NEW;
> 
>         else
> 
>                 if NEW.billing_frequency = ''Semi-Annual''
> 
>                 then
> 
>                         NEW.rate := NEW.rate/6;
>  
>                         NEW.rate_override := NEW.rate_override/6;
>         
>                         return NEW;
> 
>                 else 
> 
>                         if NEW.billing_frequency = ''Quarterly''
> 
>                         then
> 
>                                 NEW.rate := NEW.rate/3;
> 
>                                 NEW.rate_override := NEW.rate_override/3;
> 
>                                 return NEW;
> 
>                         end if;
> 
>                 end if;
> 
>         end if;
> 
> end if;
> 
> end;
> 
> 'language 'plpgsql';
> 
> drop trigger mrr_set_trigger on report_table;
> 
> create trigger mrr_set_trigger 
> 
> before insert on report_table
> 
> for each row execute procedure mrr();
> 




view thread (5+ messages)

Message-ID: <Pine.BSF.4.10.10102071307020.17745-100000@tidal.ipinc.com>
Permalink:  ../Pine.BSF.4.10.10102071307020.17745-100000@tidal.ipinc.com/
Also on:    postgresql.org/message-id/Pine.BSF.4.10.10102071307020.17745-100000@tidal.ipinc.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: jliang@ipinc.com, jeckermann@verio.net
  Subject: Re: Use of RETURN in pl/pgsql function
  In-Reply-To: <Pine.BSF.4.10.10102071307020.17745-100000@tidal.ipinc.com>
  References: <08CD1781F85AD4118E0800A0C9B8580B0948FD@NEZU> <Pine.BSF.4.10.10102071307020.17745-100000@tidal.ipinc.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox