| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: return query/composite types |
| Date: | 2009-02-20 20:55:25 |
| Message-ID: | 14625.1235163325@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Fri, Feb 20, 2009 at 3:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Use "select * from ..." instead.
> Yeah...I was thinking maybe that shouldn't be required:
If you allow both interpretations then you create a syntactic ambiguity
(at least for the case of single-column composite types). We have
historically allowed both in SQL functions, but I think that's a design
error that shouldn't be repeated in other PLs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2009-02-20 21:19:11 | Re: [Pljava-dev] Re: Should creating a new base type require superuser status? |
| Previous Message | Merlin Moncure | 2009-02-20 20:26:54 | Re: return query/composite types |