Re: patch: to_string, to_array functions

On Wed, Jul 21, 2010 at 12:08 PM, Brendan Jurd <direvus(at)gmail(dot)com> wrote:
> On 22 July 2010 01:55, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Wed, Jul 21, 2010 at 9:39 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> I am thinking so we have to do decision about string_to_array and
>>> array_to_string deprecation first.
>>
>> Well, -1 from me for deprecating string_to_array and array_to_string.
>>
>
> For what it's worth, I agree with Pavel about the current behaviour in
> core.  It's broken whenever NULLs come into play.  We need to improve
> on this one way or another, and I think it would be a shame to deal
> with a problem in core by adding something to contrib.

Fair enough. I'm OK with putting it in core if we can come up with
suitable names.

>> I am not in favor of the names to_string and to_array even if we put
>> them in contrib, though.  The problem with string_to_array and
>> array_to_string is that they aren't descriptive enough, and
>> to_string/to_array is even less so.
>
> What about implode() and explode()?  It's got symmetry and it's
> possibly more descriptive.

Hmm, it's a thought.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company