Re: patch (for 9.1) string functions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: patch (for 9.1) string functions
Date
Msg-id AANLkTinsM5o9dztt6vPecGyKiHH-aYr71izNh59_EoFZ@mail.gmail.com
Whole thread Raw
In response to Re: patch (for 9.1) string functions  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: patch (for 9.1) string functions
List pgsql-hackers
On Mon, Jul 26, 2010 at 9:10 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
>> CONCAT('foo', NULL) => 'foo' really the behavior that everyone else
>> implements here?  And why does CONCAT() take a variadic "ANY"
>> argument?  Shouldn't that be variadic TEXT?
>
> What does that accomplish, besides forcing you to sprinkle every
> concat call with text casts (maybe that's not a bad thing?)?

You could ask the same thing about the existing || operator.  And in
fact, we used to have that behavior.  We changed it in 8.3.  Perhaps
that was a good decision and perhaps it wasn't, but I don't think
using CONCAT() to make an end-run around that decision is the way to
go.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: patch (for 9.1) string functions
Next
From: "Kevin Grittner"
Date:
Subject: Re: psql \timing output supressed in quiet mode