Re: OUT parameter

From: "Daniel Caune" <daniel(dot)caune(at)ubisoft(dot)com>
To: "Owen Jacobson" <ojacobson(at)osl(dot)com>, <pgsql-sql(at)postgresql(dot)org>
Subject: Re: OUT parameter
Date: 2006-03-23 19:20:26
Message-ID: 1E293D3FF63A3740B10AD5AAD88535D201D9F9FA@UBIMAIL1.ubisoft.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


> > "Owen Jacobson" <ojacobson(at)osl(dot)com> writes:
> > > I'd say there's no problem with this, PROVIDED you can ensure
you'll
> > > never abort before completing the computation.
> >
> > Not really an issue in Postgres: we do not support pass-by-reference
> > parameters and are unlikely to start doing so. There isn't any way
> > that you can affect locals of a calling procedure before you return.
>
> Then I've misunderstood the semantics of OUT and more importantly
INOUT
> parameters. Thanks for the correction; I'm reading Daniel Caune's
notes
> on the docs now.
>
> -Owen

Funny! I started that thread on OUT parameter; that's a kind of
circle... :-)

--
Daniel CAUNE
Ubisoft Online Technology
(514) 4090 2040 ext. 5418

Browse pgsql-sql by date

  From Date Subject
Next Message Don Maier 2006-03-23 19:44:32 Expressing a result set as an array (and vice versa)?
Previous Message Owen Jacobson 2006-03-23 17:12:32 Re: OUT parameter