| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(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-12 05:33:41 |
| Message-ID: | CAFj8pRACMZxGeKsPQqYogrbK48JQ5g3gT5gMELwHoLH8CH-EGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2014/1/12 Marko Tiikkaja <marko(at)joh(dot)to>
> On 1/9/14, 2:57 PM, Dean Rasheed wrote:
>
>> Yes, this should just return the number of elements, and 0 for an empty
>> array.
>>
>> How it should behave for multi-dimensional arrays is less clear, but
>> I'd argue that it should return the total number of elements, i.e.
>> cardinality('{{1,2},{3,4}}'::int[][]) = 4. That would make it
>> consistent with the choices we've already made for unnest() and
>> ordinality:
>> - cardinality(foo) = (select count(*) from unnest(foo)).
>> - unnest with ordinality would always result in ordinals in the range
>> [1, cardinality].
>>
>
> Ignoring my proposal, this seems like the most reasonable option. I'll
> send an updated patch along these lines.
>
+1
Pavel
>
>
> Regards,
> Marko Tiikkaja
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2014-01-12 05:51:04 | plpgsql.consistent_into |
| Previous Message | Pavel Stehule | 2014-01-12 05:32:55 | have to do move ready for commit patch from previous commitfest? |