From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Sam Mason" <sam(at)samason(dot)me(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: is any reason why only one columns subselect are allowed in array()? |
Date: | 2008-11-18 16:20:27 |
Message-ID: | 162867790811180820l32a82004m186e872f66fe1ba0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2008/11/18 Sam Mason <sam(at)samason(dot)me(dot)uk>:
> On Tue, Nov 18, 2008 at 07:37:44AM -0800, David Fetter wrote:
>> On Tue, Nov 18, 2008 at 10:29:53AM -0500, Robert Haas wrote:
>> > Seems like you could just write SELECT ARRAY[col1, col2, col3]
>> > instead of SELECT col1, col2, col3.
>>
>> If I understand this right, Pavel is thinking that
>>
>> ARRAY(SELECT col1, col2, col3...)
>>
>> should produce an array each element of which is the compound type
>> consisting of (col1, col2, col3), and if it doesn't produce one, we're
>> looking at a pretty large POLA violation.
>
> I've used this syntax before and got a surprising message back. I'd
> expect to be able to do the following:
>
> ARRAY((SELECT col1, col2 FROM (VALUES ('a',1), ('b',2)) x(col1,col2)));
>
> and get the following back {"(a,1)","(b,2)"}. So I think I'm with
> David.
this is different result - it's array of records, not 2d array.
regards
Pavel
>
>
> Sam
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-11-18 16:20:50 | Re: Re: [BUGS] libpq does not manage SSL callbacks properly when other libraries are involved. |
Previous Message | Pavel Stehule | 2008-11-18 16:19:12 | Re: is any reason why only one columns subselect are allowed in array()? |