From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: to_string, to_array functions |
Date: | 2010-08-09 20:40:53 |
Message-ID: | AANLkTinO_qVjwEa1wfvdat3s3higB8xO+7RtBtGTcTQU@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 9, 2010 at 4:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>> Is there any reason why array functions need the type prefix when
>> other type conversion functions don't? Why didn't we name unnest()
>> array_unnest()?
>
> UNNEST() is in the standard, IIRC, so you'd have to ask the SQL
> committee that. (And no, they're not exactly being consistent either,
> see array_agg() for example.)
>
> But anyway, my point here is that these functions are close enough to
> the existing string_to_array/array_to_string functions that they should
> be presented as variants of those, not arbitrarily assigned unrelated
> new names. Whether we'd have chosen different names if we had it to do
> over is academic.
I don't array_agg is the same case, because you're aggregating into an
array, not from one. all the same, +1 to your names (didn't like
explode much).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-08-09 20:44:52 | Re: dynamically allocating chunks from shared memory |
Previous Message | David E. Wheeler | 2010-08-09 20:34:39 | Re: patch: to_string, to_array functions |