| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, 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-08-09 16:54:38 |
| Message-ID: | 201008091654.o79Gsc318521@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule wrote:
> 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
This email thread linked to from our TODO list explains that arrays
combined with NULLs have many inconsistenciess:
http://archives.postgresql.org/pgsql-bugs/2008-11/msg00009.php
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Oliveira | 2010-08-09 17:14:54 | Re: Universal B-tree |
| Previous Message | Greg Stark | 2010-08-09 16:54:35 | Re: Universal B-tree |