List:General Discussion« Previous MessageNext Message »
From:Peter Brawley Date:May 10 2005 8:53pm
Subject:Re: Comparing to null queries
View as plain text  

If 3.23.22 gave (NULL != 1) = TRUE,/ that/ was a bug, because in SQL, 
(NULL != 1) is NULL.

This 3.23.26 change history item might be your culprit: "Fixed `<>' to 
work properly with `NULL'."



Mike Rykowski wrote:

>I have a query:
>select * from table where del != "1";
>Let's assume that I have a record where del is null (del is a single
>character field).
>In version 3.23.22-beta I get the record returned with the above query,
>in version 4.1.10a I get nothing returned.
>Did something change between these versions or is this a bug?  I
>couldn't find anything specific to this on the archives.

Attachment: [text/html]
No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.8 - Release Date: 5/10/2005
Comparing to null queriesMike Rykowski10 May
  • Re: Comparing to null queriesmfatene10 May
  • Re: Comparing to null queriesMichael Stassen10 May
  • Re: Comparing to null queriesPeter Brawley10 May