Found this bug through some automatically generated code:
create table things (
id int,
name varchar(20)
);
create table categories (
thing_id int,
category varchar(20)
);
insert into things values(1, 'one');
insert into things values(2, 'two');
insert into things values(3, 'three');
insert into categories values(2, 'cat');
A: select * from things t left join categories c on t.id = c.thing_id
where (c.category = 'xx');
B: select * from things t left join categories c on t.id = c.thing_id
where (c.category = 'xx' OR c.category = 'xx');
C: select * from (select * from things t left join categories c on t.id
= c.thing_id) d where (d.category = 'xx');
D: select * from (select * from things t left join categories c on t.id
= c.thing_id) d where (d.category = 'xx' OR d.category = 'xx');
None of the statements A to D should return any results but statement B
does, incorrectly. D seems to be a suitable workaround (for me,
anyway).
There seem to be plenty of other outer join problem reports on the list,
many of them very old, and yet it still doesn't work. This does not
inspire much confidence in SAPDB/MaxDB ...
Andy.
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]