Re: string || NULL ambiguity

Oleg Bartunov <oleg@sai.msu.su> writes:
> we have a little problem in new version of tsearch we're currently
> working. We've implemented concatenation operation for txtidx type
> and treat concatenation with NULL as NULL (as it should be).
> But people get confused with such behaivour. Do we obliged to
> follow NULL rule ? It seems more natural in case of text searching to treat
> stringA||NULL as stringA.

This seems a very bad idea.  If you think people are confused by NULLs
now, it'll be ten times worse if some datatypes handle them differently
from others.
        regards, tom lane