Peter Brawley wrote:
Giuseppe,
>mysql> select 2 not in (1,null,3);
>+-+
>| 2 not in (1,null,3) |
>+-+
>|NULL |
>+-+
>1 row in set (0.00 sec)
># NOT OK
Isn't that standard SQL behaviour?
Yes, it is. As I said before
Giuseppe,
>mysql> select 2 not in (1,null,3);
>+-+
>| 2 not in (1,null,3) |
>+-+
>|NULL |
>+-+
>1 row in set (0.00 sec)
># NOT OK
Isn't that standard SQL behaviour? NULL is not a value. NOT IN compares
the values using '='
In article <[EMAIL PROTECTED]>,
Giuseppe Maxia <[EMAIL PROTECTED]> writes:
> The whole point is actually in subqueries, not when using IN or NOT IN in a
> normal query.
> The bug occurs when a NOT IN is used in a subquery as a LEFT JOIN replacement.
> SELECT something from t1 where column1 NOT I
Dan Nelson wrote:
In the last episode (Mar 16), Giuseppe Maxia said:
Here is a description of what looks like a serious bug. This is
related to bugs #7294 and #6247
Tested against mysql 4.1.9 and 4.1.10.
Description:
operator NOT IN fails when a subquery returns one or more NULL
values.
How-To
In the last episode (Mar 16), Giuseppe Maxia said:
> Here is a description of what looks like a serious bug. This is
> related to bugs #7294 and #6247
>
> Tested against mysql 4.1.9 and 4.1.10.
>
> >Description:
> operator NOT IN fails when a subquery returns one or more NULL
> value
Hi.
Here is a description of what looks like a serious bug.
This is related to bugs #7294 and #6247
Tested against mysql 4.1.9 and 4.1.10.
Cheers
Giuseppe Maxia
>Description:
operator NOT IN fails when a subquery returns one or more NULL values.
>How-To-Repeat:
simple proof of conce
