Re: Proposal: stand-alone composite types

Christopher Kings-Lynne <chriskl@familyhealth.com.au>

From: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
To: "Joe Conway" <mail@joeconway.com>, "pgsql-hackers" <pgsql-hackers@postgresql.org>
Date: 2002-07-30T06:00:46Z
Lists: pgsql-hackers
> 3. Modify CREATE FUNCTION to allow the implicit creation of a dependent
>     composite type, e.g.:
>
>     CREATE [ OR REPLACE ] FUNCTION name ( [ argtype [, ...] ] )
>     RETURNS [setof] { data_type | (column_name data_type [, ... ]) }...
>
>     This would automatically create a stand-alone composite type with a
>     system generated name for the function. Thanks to the new dependency
>     tracking, the implicit composite type would go away if the function
>     is dropped.
>
>
> Comments, objections, or thoughts?

I'm just licking my lips in anticipation of converting my entire website to
SRFs ;)

Chris