Andreas Joseph Krogh wrote:
If aggregates ignore NULL one could argue that so shuld the ||-operator?
I agree that this behaviour may seem pedantic, but changing this is only
going to lead to a huge wtf? factor. The baviour for NULL in aggregates
is pretty well documented and known. Even MySQL returns NULL in this
case, and they are known todo all sorts of changes for better "ease of use".
If you want this behaviour you will have to explicitly handle it with
COALESCE().
regards,
Lukas
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
