David,
- Original Message -
From: "David Mechner" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Wednesday, November 20, 2002 1:59 PM
Subject: Re[2]: delete where column <=> null
> Ok, so it seems to be a bug. What's the procedure for report
just what the world needs: more non-standard sql
syntax.
> Ok, so it seems to be a bug. What's the procedure for reporting it (or
> do the developers read this list?)
>
> -David
> A minimal test case that demonstrates the bug:
> create table t (
> id integer,
> index id_idx(id)
> );
> in
At 15:58 -0500 11/19/02, David Mechner wrote:
Ok, so it seems to be a bug. What's the procedure for reporting it
Check the manual:
http://www.mysql.com/doc/en/Bug_reports.html
-
Before posting, please check:
http://www.mysq
Ok, so it seems to be a bug. What's the procedure for reporting it (or
do the developers read this list?)
-David
A minimal test case that demonstrates the bug:
create table t (
id integer,
index id_idx(id)
);
insert into t(id) values(null);
select * from t;
delete from t where id <=> 1;
es below using <=>, the
> records containing NULL *are* deleted. I'm not sure why David is
observing
> different behavior.
>
> >
> >-Original Message-
> >From: Andrew Braithwaite [mailto:[EMAIL PROTECTED]]
> >Sent: Tuesday, November 19, 2002 12:26 PM
Hi.
On Tue 2002-11-19 at 12:38:33 -0500, [EMAIL PROTECTED] wrote:
> Nothing can be compared to null, not even null, which implies that MySQL is
> wrong in returning two rows in the SELECT.
I have to disagree. The "<=>" operator is explicitly defined to allow
that. "<=>" is the same as "=", except
Tuesday, November 19, 2002 12:26 PM
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject: RE: delete where column <=> null
David,
I get the same behaviour with mysql 3.23.47 (not max) and with mysql v
4.0.4-beta
Without the index it works fine. Must be a bug
Cheer
ember 2002 17:39
To: Andrew Braithwaite; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: delete where column <=> null
Nothing can be compared to null, not even null, which implies that MySQL is
wrong in returning two rows in the SELECT. Your query needs to say IS NULL:
delete from t wher
: Tuesday, November 19, 2002 12:26 PM
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject: RE: delete where column <=> null
David,
I get the same behaviour with mysql 3.23.47 (not max) and with mysql v
4.0.4-beta
Without the index it works fine. Must be a bug
Cheers,
Andre
r 20, 2002 1:45 AM
> To: [EMAIL PROTECTED]
> Subject: delete where column <=> null
>
>
> Hi,
>
> I'm trying to delete from a table where col <=> null, but it doesn't
> seem to work. I don't see anything in the manual that says that <=
: delete where column <=> null
Hi,
I'm trying to delete from a table where col <=> null, but it doesn't seem to
work. I don't see anything in the manual that says that <=> can't be used in
the where clause of a delete statment, but:
mysql>
Hi,
I'm trying to delete from a table where col <=> null, but it doesn't
seem to work. I don't see anything in the manual that says that <=>
can't be used in the where clause of a delete statment, but:
mysql> select * from t;
++--+
| id | num |
++--+
| 1 | NULL |
| 1 | NULL |
12 matches
Mail list logo