From: | Florian Pflug <fgp(at)phlo(dot)org> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, PostGreSql hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: array_length(anyarray) |
Date: | 2014-01-10 12:00:05 |
Message-ID: | 01189A16-1D84-4F35-9022-9AABCB1960BB@phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan10, 2014, at 11:00 , Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Fri, Jan 10, 2014 at 3:52 AM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
>> On 1/10/14, 10:41 AM, Merlin Moncure wrote:
>>>
>>> What's needed for better iteration support (IMO)
>>> is a function that does what unnest does but returns an array on
>>> indexes (one per dimsension) -- a generalization of the
>>> _pg_expandarray function. Lets' say 'unnest_dims'.
>>
>>
>> So unnest_dims('{{1,2},{3,4}}'::int[]) would return VALUES (1,
>> '{1,2}'::int[]), (2, '{3,4}'::int[])? If so, then yes, that's a
>> functionality I've considered us to have been missing for a long time.
>
> not quite. it returns int[], anyelement: so, using your example, you'd get:
>
> [1,1], 1
> [1,2], 2
> [2,1], 3
> [2,2], 4
Now that we have WITH ORDINALITY, it'd be sufficient to have a
variant of array_dims() that returns int[][] instead of text, say
array_dimsarray(). Your unnest_dims could then be written as
unnest(array_dimsarray(array)) with ordinality
best regards,
florian pflug
From | Date | Subject | |
---|---|---|---|
Next Message | Florian Pflug | 2014-01-10 12:49:31 | Re: [PATCH] Negative Transition Aggregate Functions (WIP) |
Previous Message | Andres Freund | 2014-01-10 11:29:42 | Re: [PATCH] Relocation of tablespaces in pg_basebackup |