Re: [HACKERS] string_to_array with empty input

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: justin <justin(at)emproshunts(dot)com>, Greg Stark <stark(at)enterprisedb(dot)com>, Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] string_to_array with empty input
Date: 2009-04-01 21:33:29
Message-ID: 603c8f070904011433m6b094e97j4f1354181f166bf2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Wed, Apr 1, 2009 at 5:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Or we could stick to the current behavior and say "use COALESCE() to
> resolve the ambiguity, if you need to".

If there's no consensus on changing the behavior, it's probably better
to be backward compatible than not.

...Robert

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steve Crawford 2009-04-02 00:31:30 Re: [HACKERS] string_to_array with empty input
Previous Message Robert Haas 2009-04-01 21:31:07 Re: [GENERAL] string_to_array with empty input

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-04-01 21:41:53 Re: [Snowball-discuss] Snowball release cycle ?
Previous Message Robert Haas 2009-04-01 21:31:07 Re: [GENERAL] string_to_array with empty input