From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: to_string, to_array functions |
Date: | 2010-07-21 05:51:24 |
Message-ID: | AANLkTillZkJSNsUgMOZojY9ylZkJ0VhinSGsibOrC_cd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/7/21 Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>:
> 2010/7/20 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
>> here is a new version - new these functions are not a strict and
>> function to_string is marked as stable.
>
> We have array_to_string(anyarray, text) and string_to_array(text, text),
> and you'll introduce to_string(anyarray, text, text) and
> to_array(text, text, text).
I have to repeat it, the behave of this functions are little bit
different. string_to_array and array_to_string are buggy.
* it isn't support a NULL
* it doesn't differentiate a empty array and NULL
* we cannot to change default behave of existing functions
* array_to_string is badly marked as IMMUTABLE
> Do we think it is good idea to have different names for them? IMHO, we'd
> better use 3 arguments version of array_to_string() instead of the
> new to_string() ?
>
> If to_string and to_array is in the SQL standard, we can accept the
> name changes.
> But if there are no standard, I'd like to keep the existing function names.
>
no it isn't in standard, but I am thinking, so we have to gently alone
a old functions
Regards
Pavel Stehule
> --
> Itagaki Takahiro
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2010-07-21 06:29:49 | Re: patch (for 9.1) string functions |
Previous Message | KaiGai Kohei | 2010-07-21 05:41:52 | Re: leaky views, yet again |