Before a few months, I was working on some mysterious issue regarding some SQL statements, it was something like this.
SELECT count(*) from some_table WHERE (condition_a);
the result was:

+----------+
| count(*) |
+----------+
|   11223  |
+----------+

alright Now:
SELECT count(*) from some_table WHERE (condition_a) AND (condition_b);

+----------+
| count(*) |
+----------+
|     0    |
+----------+
aha Ok then:
SELECT count(*) from some_table WHERE condition_a AND NOT (condition_b);
The result was also
Before a few months, I was working on some mysterious issue regarding some SQL statements, it was something like this.
SELECT count(*) from some_table WHERE (condition_a);
the result was:

+----------+
| count(*) |
+----------+
|   11223  |
+----------+

alright Now:
SELECT count(*) from some_table WHERE (condition_a) AND (condition_b);

+----------+
| count(*) |
+----------+
|     0    |
+----------+

HA !!!!
Ok for those 11223 records the condition_a was true, from the second statement I could tell that condition_b was false, so NOT condition_b should be true, but it was also false from the third statement.
So for Logic to play around condition_b, and NOT condition_b both are false (How can that be) all theories of logic are broken (what is going on?)
After breaking up the two conditions, I found that I was comparing one of the values in condition_b with NULL, so in BOTH cases the result would be FALSE (or actually UNKNOWN which is casted to NULL), I’ve always assumed that NULL would be casted to 0, but the fact that it’s not.
So this was just a thing that you might want to take care of when you write your SQL statements.
Hope it was Useful