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

Re: Proposal: stand-alone composite types

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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


In response to

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2002-07-30 06:06:27
Subject: Weird manual page
Previous:From: Thomas LockhartDate: 2002-07-30 05:56:49
Subject: Re: WAL file location

pgsql-patches by date

Next:From: Christopher Kings-LynneDate: 2002-07-30 06:55:35
Subject: DROP COLUMN round 4
Previous:From: Joe ConwayDate: 2002-07-30 05:50:41
Subject: Proposal: stand-alone composite types

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group