| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | James <james(at)mercstudio(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #2417: bug for finding string in column |
| Date: | 2006-05-02 22:17:05 |
| Message-ID: | 20060502151240.B86001@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, 2 May 2006, James wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2417
> Logged by: James
> Email address: james(at)mercstudio(dot)com
> PostgreSQL version: 8.1
> Operating system: Microsoft Windows XP Professional
> Description: bug for finding string in column
> Details:
>
> hi,
>
> i've encounter bug where when a field is empty / null (type varchar(255) ),
> when i use the sql query <> 'myvalue', it seems to be false all the time.
If it's null, it's actually returning unknown (not true or false) and
as far as we know that's not a bug because that's how SQL defines the
comparison operators.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2006-05-03 00:05:00 | Re: BUG #2417: bug for finding string in column |
| Previous Message | Peter Brant | 2006-05-02 16:42:33 | Re: BUG #2371: database crashes with semctl failed |