From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Joe Conway" <mail(at)joeconway(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: stand-alone composite types |
Date: | 2002-07-30 06:00:46 |
Message-ID: | GNELIHDDFBOCMGBFGEFOKEGJCDAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2002-07-30 06:06:27 | Weird manual page |
Previous Message | Thomas Lockhart | 2002-07-30 05:56:49 | Re: WAL file location |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2002-07-30 06:55:35 | DROP COLUMN round 4 |
Previous Message | Joe Conway | 2002-07-30 05:50:41 | Proposal: stand-alone composite types |