Skip site navigation (1) Skip section navigation (2)

Re: Found small issue with OUT params

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Found small issue with OUT params
Date: 2005-09-29 02:21:00
Message-ID: 200509290221.j8T2L0311481@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> writes:
> > Please don't take this the wrong way, but don't you think even if a 
> > single param is declared as OUT it should return the name of the OUT param?
> 
> Not really, because "create function foo (in x int, out y float)" is
> supposed to have the same external behavior as "create function foo
> (in x int) returns float".  I agree it's a bit of a judgment call, but
> I do not see a case for changing it.

I am agreeing with the poster that use of OUT should always print the
out parameter name.  Is there a downside to doing that?  Seems it gives
people an option.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-09-29 02:22:50
Subject: Re: Open items list for 8.1
Previous:From: Jonah H. HarrisDate: 2005-09-29 02:16:06
Subject: Re: [HACKERS] Added documentation about caching, reliability

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group