From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | 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-20 14:06:12 |
Message-ID: | CAEZATCVf2oZ73K5fpf8m6PU6EncOoEE3SWXVAEi8DvnkEKLSQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 20 January 2014 13:47, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> On 1/20/14 2:29 PM, Dean Rasheed wrote:
>>
>> I think this is ready for committer
>
>
> Thanks!
>
>> ... although I would also like to see
>>
>> the doc changes to make the table of array function descriptions a bit
>> more explicit about corner cases.
>
>
> Hmm. I completely missed the fact that unnest() already uses a structure
> similar to yours. It looks like e.g. window functions do the same, but JSON
> functions all have proper capitalization and periods, and some others
> capitalize but omit periods.
>
> I could submit a separate patch to describe array functions in a bit more
> detail,
Yes please. I think that would be helpful.
> I'm not planning on fixing the
> inconsistencies, though, despite them annoying me.
>
To be honest, I hadn't even noticed those inconsistencies. The main
thing is to alert new users to the fact that empty arrays behave in a
rather odd way for a couple of those functions.
Regards,
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2014-01-20 14:14:02 | Re: ALTER TABLESPACE ... MOVE ALL TO ... |
Previous Message | Marko Tiikkaja | 2014-01-20 13:47:19 | Re: array_length(anyarray) |