| From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: what is good solution for support NULL inside string_to_array function? |
| Date: | 2010-05-07 17:53:10 |
| Message-ID: | 4BE45386.9010109@pinpointresearch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>
>>> quietly removing NULL is maybe good for compatibility but is wrong for
>>> functionality.
>>>
>
>
>> I agree. I wasn't aware of this little misfeature.
>>
>
>
>> Default display for NULL should be a zero-length string.
>>
>
> That's just as broken as Pavel's suggestion. Unless you have something
> that is guaranteed distingishable from the output of any non-null value,
> you really can't make a significant improvement here.
>
> regards, tom lane
>
>
Is this, perhaps, a generalized case of this long-running discussion
from last year?:
http://archives.postgresql.org/pgsql-hackers/2009-03/msg01350.php
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-05-07 17:56:13 | Re: no universally correct setting for fsync |
| Previous Message | Tom Lane | 2010-05-07 15:31:40 | Re: beta to release |