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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Wed, 28 Sep 2005 22:21:00 -0400 (EDT)
  • Message-id: <200509290221(dot)j8T2L0311481(at)candle(dot)pha(dot)pa(dot)us>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group