"P.Peti" wrote:
Hello,
Thanx for the answers, I think I've got the point now. I
have one more doubt though. You described me that this
whole thing with the comparison not working with NULL
values is obvious. Why did it work in 3.22.25 then?
Thank you for the answers so far.
Bye:
Hello,
I have updated my mysql server from version 3.22.25 to
3.23.33. I've noticed that the same query's output I've run
in the old version differs from the new version's.
Eg.
I've got a film database:
SELECT COUNT(*) FROM FILM;
returns me a number of 53.
The same select with a WHERE
And
SELECT COUNT(*) FROM FILM WHERE COMMENT IS NULL:
returns what?
"P.Peti" wrote:
Hello,
I have updated my mysql server from version 3.22.25 to
3.23.33. I've noticed that the same query's output I've run
in the old version differs from the new version's.
Eg.
I've got a film
Hello,
And
SELECT COUNT(*) FROM FILM WHERE COMMENT IS NULL:
returns what?
Sure, I forgot to mention that I know it's all about the
NULL values, i can correct the "problem" (maybe not a
problem but I think it's a weird behavior) i just don't
understand why?
The query you mentioned returns
"P.Peti" wrote:
Hello,
And
SELECT COUNT(*) FROM FILM WHERE COMMENT IS NULL:
returns what?
Sure, I forgot to mention that I know it's all about the
NULL values, i can correct the "problem" (maybe not a
problem but I think it's a weird behavior) i just don't
understand why?
The
Hello P.Peti,
Monday, March 12, 2001, 11:17:16 PM, you wrote:
PP It just seems to be weird that a subset and its complement
PP does not equal the whole table. So the thing is:
PP #"!deleted" doesn't include "#NULL" as the set filtered by
PP the clause 'WHERE comment!="deleted"' doesn't
Hello,
Thanx for the answers, I think I've got the point now. I
have one more doubt though. You described me that this
whole thing with the comparison not working with NULL
values is obvious. Why did it work in 3.22.25 then?
Thank you for the answers so far.
Bye:
PP.
