Re: Different behaviour of concate() and concate operator ||

Поиск
Список
Период
Сортировка
От amul sul
Тема Re: Different behaviour of concate() and concate operator ||
Дата
Msg-id 1398750466.36734.YahooMailNeo@web193501.mail.sg3.yahoo.com
обсуждение исходный текст
Ответ на Re: Different behaviour of concate() and concate operator ||  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Monday, 28 April 2014 10:56 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Greg Stark <stark@mit.edu> writes:

>So they pretty much would have to make concat() treat NULL as empty.


could it be problematic if I update pg_operator catalogue entry for ||, 
call to concat() function instead of texcat(), in my production environment ? 

for eg.
 oprname | oprleft | oprright | oprresult | oprcode
---------+---------+----------+-----------+---------
 ||      |    25   |   25     |     25    | concat
(1 row)


result would be 

test=# select  'abc' || NULL;                                                                            ;
 ?column?
----------
 abc
(1 row)

Thank for your help.

Regards,
Amul Sul



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Sergey Muraviov
Дата:
Сообщение: Re: Problem with displaying "wide" tables in psql
Следующее
От: Dilip kumar
Дата:
Сообщение: Re: Proposal for Merge Join for Non '=' Operators