Re: Proposal: stand-alone composite types - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Proposal: stand-alone composite types
Date
Msg-id GNELIHDDFBOCMGBFGEFOKEGJCDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Proposal: stand-alone composite types  (Joe Conway <mail@joeconway.com>)
List 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



pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: WAL file location
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Weird manual page