From: | Robert Haas |
---|---|
To: | Tom Lane |
Cc: | "David E(dot) Wheeler" |
Subject: | Re: [HACKERS] string_to_array with empty input |
Date: | 2009-04-02 18:37:21 |
Message-ID: | [email protected] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Thu, Apr 2, 2009 at 2:18 PM, Tom Lane
> Robert Haas
>> On Thu, Apr 2, 2009 at 2:04 PM, Tom Lane
>>> Right at the moment, if we stick with the historical definition
>>> of the function, *both* camps have to write out their choice of
>>> the above. Seems like this is the worst of all possible worlds.
>>> We should probably pick one or the other.
>
>> ISTM there are three camps.
>
> If there's a camp that actually *wants* a NULL result for this case,
> I missed the reasoning. AFAICS we can either say that every application
> is going to have to put in a CASE wrapper around this function, or say
> that we'll make it do the right thing for some of them and the rest have
> to put the same wrapper around it.
So that we don't break existing apps because of an issue that is
trivial to work around.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-04-02 18:50:57 | Re: [HACKERS] string_to_array with empty input |
Previous Message | Sam Mason | 2009-04-02 18:24:16 | Re: [HACKERS] string_to_array with empty input |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2009-04-02 18:37:33 | Re: [HACKERS] Mentors needed urgently for SoC & PostgreSQL Student Internships |
Previous Message | Mokhtari Amine | 2009-04-02 18:34:38 | Re: about hacking postgresql |