From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl> |
Subject: | Re: patch (for 9.1) string functions |
Date: | 2010-07-26 19:07:08 |
Message-ID: | AANLkTin51OW-=ntjiajOw_T_y6azX9J1WOsVU3KDoLmV@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 26, 2010 at 2:09 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I understand, but with only text accepting, then CONCAT will has much
> less benefit - you can't do a numeric list, for example
>
> see concat(c1::text, ',', c2::text, ',' ...)
>
> with this is much simpler use a pipes '' || c1 || ',' || c2 ... and
> this operator does necessary cast self.
>
> This function is probably one use case of exception from our rules.
At least two, right? Because for that use case you'd probably want
concat_ws(). In fact, it's hard for me to think of a variadic text
function where you wouldn't want the "no casts" behavior you're
getting via ANY.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-07-26 19:16:27 | Re: dynamically allocating chunks from shared memory |
Previous Message | Robert Haas | 2010-07-26 18:56:37 | Re: dynamically allocating chunks from shared memory |