Re: patch (for 9.1) string functions
От | Robert Haas |
---|---|
Тема | Re: patch (for 9.1) string functions |
Дата | |
Msg-id | AANLkTinsM5o9dztt6vPecGyKiHH-aYr71izNh59_EoFZ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: patch (for 9.1) string functions (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: patch (for 9.1) string functions
|
Список | 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 по дате отправления: