| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: array_to_string bug? |
| Date: | 2009-11-12 18:33:41 |
| Message-ID: | 603c8f070911121033n7f741473kbcdd1ce7089b0ef3@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 12, 2009 at 1:28 PM, Steve Crawford
<scrawford(at)pinpointresearch(dot)com> wrote:
> Although it might cause a fair amount of backward-compatibility trouble, the
> string representation could either use NULL to represent a null element as
> is allowed in other contexts or require that empty-string elements be
> represented as "" to differentiate ,"", (empty-string element) from ,, (null
> element).
That would cause a substantial amount of grief to people who might not
want that behavior, though. I use these functions for creating
human-readable output, not for serialization. Simple, predictable
behavior is very important.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2009-11-12 18:36:51 | Re: next CommitFest |
| Previous Message | Robert Haas | 2009-11-12 18:32:15 | Re: next CommitFest |