| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PostGreSql hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: array_length(anyarray) |
| Date: | 2014-01-18 03:07:21 |
| Message-ID: | 52D9EFE9.20608@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/12/14, 5:53 AM, I wrote:
> On 1/9/14, 2:57 PM, Dean Rasheed wrote:
>> 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.
Here's the patch as promised. Thoughts?
Regards,
Marko Tiikkaja
| Attachment | Content-Type | Size |
|---|---|---|
| cardinality.patch | text/plain | 5.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-18 03:17:28 | Re: [PATCH] Make various variables read-only (const) |
| Previous Message | Tom Lane | 2014-01-18 02:01:01 | Re: Minor improvements to sslinfo contrib module |