Hi!
Nachdem MySql selbst bloss kostenpflichtigen Support bietet und mir trotz intensiver Bemühungen nicht möglich war, kostenlos einen Bug zu Reporten, will ich hier das Thema auf das Tablett bringen:
I've a very dirty bug costing me hours uptill now; maybe it is related
with the AND/OR-behavior described in the releasenote of 3.23.52/53;
A query once runs with release 3.23.53 (my own PC); same query don't
work with release 3.23.51 (my Host-Provider).
Here is the Query:
----
SELECT * FROM tb_category cat1
LEFT JOIN tb_category cat2 ON
cat1.parent = cat2.id
WHERE cat2.id IS NULL
OR cat1.parent = 0
ORDER BY cat1.name;
----
The actual right result is a set of rows, where at least cat1.parent
>=0
and cat1.id >=0;
I need all rows, who don't have an parent (parent=0) **or** a given
parent doesn't exist (cat2.id is null).
The actual false result is a set of rows, where **all** columns are
NULL.
So, this query works fine with 3.23.53, also woked fine in the past
with
older realse of MySQL.
Now, it don't work since weeks at my old Webspaceprovider and at my
current one. I took the action to change the provider (now i've to pay
for!) to get a solution. The new provider has release 3.23.51.
I can't belive that this is config-related.
Please, would you be so kind and check some possible bugs??
Thank you very much
Regards
Sam
This is all base on following structure & data:
----
CREATE TABLE tb_category (
id int(10) unsigned NOT NULL auto_increment,
name char(50) NOT NULL default '',
parent int(10) unsigned NOT NULL default '0',
updated datetime default NULL,
created datetime default NULL,
nameauthor char(30) default NULL,
PRIMARY KEY (id),
UNIQUE KEY k_parentname (parent,name)
) TYPE=MyISAM;
INSERT INTO tb_category VALUES (1, 'News', 0, NULL, '2002-09-11
23:42:27', 'god');
INSERT INTO tb_category VALUES (3, 'das', 1, NULL, '2002-09-12
01:19:08', 'god');
INSERT INTO tb_category VALUES (4, 'sausua', 1, NULL, '2002-09-12
02:05:21', 'god');
Nachdem MySql selbst bloss kostenpflichtigen Support bietet und mir trotz intensiver Bemühungen nicht möglich war, kostenlos einen Bug zu Reporten, will ich hier das Thema auf das Tablett bringen:
I've a very dirty bug costing me hours uptill now; maybe it is related
with the AND/OR-behavior described in the releasenote of 3.23.52/53;
A query once runs with release 3.23.53 (my own PC); same query don't
work with release 3.23.51 (my Host-Provider).
Here is the Query:
----
SELECT * FROM tb_category cat1
LEFT JOIN tb_category cat2 ON
cat1.parent = cat2.id
WHERE cat2.id IS NULL
OR cat1.parent = 0
ORDER BY cat1.name;
----
The actual right result is a set of rows, where at least cat1.parent
>=0
and cat1.id >=0;
I need all rows, who don't have an parent (parent=0) **or** a given
parent doesn't exist (cat2.id is null).
The actual false result is a set of rows, where **all** columns are
NULL.
So, this query works fine with 3.23.53, also woked fine in the past
with
older realse of MySQL.
Now, it don't work since weeks at my old Webspaceprovider and at my
current one. I took the action to change the provider (now i've to pay
for!) to get a solution. The new provider has release 3.23.51.
I can't belive that this is config-related.
Please, would you be so kind and check some possible bugs??
Thank you very much
Regards
Sam
This is all base on following structure & data:
----
CREATE TABLE tb_category (
id int(10) unsigned NOT NULL auto_increment,
name char(50) NOT NULL default '',
parent int(10) unsigned NOT NULL default '0',
updated datetime default NULL,
created datetime default NULL,
nameauthor char(30) default NULL,
PRIMARY KEY (id),
UNIQUE KEY k_parentname (parent,name)
) TYPE=MyISAM;
INSERT INTO tb_category VALUES (1, 'News', 0, NULL, '2002-09-11
23:42:27', 'god');
INSERT INTO tb_category VALUES (3, 'das', 1, NULL, '2002-09-12
01:19:08', 'god');
INSERT INTO tb_category VALUES (4, 'sausua', 1, NULL, '2002-09-12
02:05:21', 'god');
Kommentar