Re: Comparing to null queries

2005-05-10 Thread Peter Brawley
Mike, 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'." PB - Mike Rykowski wrote: Hello, I have a query: select * from table where del != "1";

Re: Comparing to null queries

2005-05-10 Thread Michael Stassen
Mike Rykowski wrote: Hello, 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 c

Re: Comparing to null queries

2005-05-10 Thread mfatene
Hi, 'l' is neither equal to null nor different from null. you can try select ('l'!=NULL) or select ('l'=NULL). in 4.1.x you should write : select * from table where del != l' or del is null; mysql> select * from tbl; +--+ | del | +--+ | NULL | | a| | b| | l| | m| | l

Comparing to null queries

2005-05-10 Thread Mike Rykowski
Hello, 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 th