string || NULL ambiguity
Oleg Bartunov <oleg@sai.msu.su>
From: Oleg Bartunov <oleg@sai.msu.su>
To: Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2003-03-19T19:26:05Z
Lists: pgsql-hackers
Hi there, 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. Regards, Oleg _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83