Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Cast as compound type
- From: David Fetter <david(at)fetter(dot)org>
- To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
- Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Cast as compound type
- Date: Sun, 30 Mar 2008 13:15:24 -0700
- Message-id: <20080330201524.GB12289@fetter.org> <text/plain>
On Sun, Mar 30, 2008 at 10:00:33PM +0200, Pavel Stehule wrote: > Hello > > maybe I don't understand well your idea. There exist simple syntax - > table function > > http://archives.postgresql.org/pgsql-patches/2007-02/msg00341.php > > and it is standard It's completely different from your patch, which specifies the return type at the time you create the function. This idea takes functions which return SETOF RECORD, that is functions which determine their return type at run time instead of create time, and short-cuts the cast that you need to do at run time. Cheers, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
- References:
- Cast as compound type
- From: David Fetter
- Re: Cast as compound type
- From: Pavel Stehule
- Cast as compound type
- Prev by Date: Re: Cast as compound type
- Next by Date: Re: Submission of Feature Request : RFC- for Implementing Transparent Data Encryption in Postgres
- Previous by thread: Re: Cast as compound type
- Next by thread: Re: Cast as compound type
- Indexes: