From: | "John Jawed" <johnjawed(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Improving ALTER TYPE support |
Date: | 2006-05-24 20:50:41 |
Message-ID: | a9eb35850605241350i746fecccm865f28deb3cfa07@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ok, this way works and the proposed way isn't necessary.
On 5/24/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "John Jawed" <johnjawed(at)gmail(dot)com> writes:
> > I guess I don't understand what one has to do with the other (SRF's
> > returning records and OUT parameters). I always thought they were exclusive,
> > could you elaborate?
>
> (BTW, please don't post uselessly HTML-ified mail.)
>
> If you write something like
>
> create function foo (in p1 int, out r1 int, out r2 text)
> returns setof record
>
> then you've effectively got a function returning an anonymous composite
> type (here, with one int and one text column). I don't see a case for
> inventing a separate facility that will pretty much just duplicate this
> functionality.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-05-24 21:06:49 | Re: file-locking and postmaster.pid |
Previous Message | Alvaro Herrera | 2006-05-24 20:40:04 | Re: file-locking and postmaster.pid |