Request a Demo
Home   >   mailing lists

Re: Different behaviour of concate() and concate operator || - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Different behaviour of concate() and concate operator ||
Date
Msg-id 9231.1398692788@sss.pgh.pa.us
Whole thread Raw
In response to Different behaviour of concate() and concate operator ||  (amul sul <sul_amul@yahoo.co.in>)
Responses Re: Different behaviour of concate() and concate operator ||
List pgsql-hackers
Tree view 
amul sul <sul_amul@yahoo.co.in> writes:
> concat function and operator || have different behaviour, if any input is NULL.

The behavior of || is specified by the SQL standard, and it says (SQL99
6.27 <string value expression> general rule 2a):
           a) If either S1 or S2 is the null value, then the result of the             <concatenation> is the null
value.

So no, we're not changing it to be more like concat().
        regards, tom lane

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: shm_mq inconsistent behavior of SHM_MQ_DETACHED
Next
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Can't completely get rid of #ifndef FRONTEND in palloc.h :-(