On Mon, Jul 26, 2010 at 9:10 AM, Merlin Moncure <mmonc...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
