Re: string || NULL ambiguity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>, neilc(at)samurai(dot)com, alvherre(at)dcc(dot)uchile(dot)cl, pgsql-hackers(at)postgresql(dot)org
Subject: Re: string || NULL ambiguity
Date: 2003-03-20 14:55:03
Message-ID: 23063.1048172103@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:
> On Thu, 20 Mar 2003, Thomas T. Thai wrote:
>> Note the error: "ERROR: Void value" above. Why is that happening?

> That's because NULL is forbidden for txtidx. We'll fix that.

Please note that an empty string is not the same as NULL. The error
message in txtidx_in appears to be griping about an empty string,
not NULL.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-03-20 15:18:12 Re: Varchar Vs. Text index matching - why different?
Previous Message Tom Lane 2003-03-20 14:49:30 Re: Faster NUMERIC implementation