| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: string || NULL ambiguity |
| Date: | 2003-03-20 04:14:43 |
| Message-ID: | 20087.1048133683@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Oleg Bartunov <oleg(at)sai(dot)msu(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2003-03-20 04:22:21 | Re: A bad behavior under autocommit off mode |
| Previous Message | Bruce Momjian | 2003-03-20 04:14:01 | Re: A bad behavior under autocommit off mode |