Florian Rieffel wrote: > I'm using the latest Version of MaxDB 7.5.0.14. > > To demonstrate the problem, I've created this tables with content: > > ----------------------------------------- > > CREATE TABLE test_1 ( > id int, > primary key (id) > ) > > CREATE TABLE test_2 ( > id int, > primary key (id) > ) > > CREATE TABLE test_3 ( > id int, > primary key (id) > ) > > INSERT INTO test_1 VALUES (1) > INSERT INTO test_1 VALUES (2) > INSERT INTO test_1 VALUES (3) > INSERT INTO test_1 VALUES (4) > > INSERT INTO test_2 VALUES (1) > INSERT INTO test_2 VALUES (2) > INSERT INTO test_2 VALUES (3) > > INSERT INTO test_3 VALUES (1) > INSERT INTO test_3 VALUES (2) > INSERT INTO test_3 VALUES (3) > > ----------------------------------------- > > Well, here is my first SELECT with outer join: > > ----------------------------------------- > SELECT T1.ID,T2.ID,T3.ID > FROM TEST_1 T1,TEST_2 T2, TEST_3 T3 > WHERE T3.ID = T1.ID AND T1.ID = T2.ID(+) > > Result: > 1,1,1 > 2,2,2 > 3,3,3 > ----------------------------------------- > > The Result of the first SELECT seems to be ok. > > But now, I change the position of TEST_1 with TEST_3 in the FROM list > and it appears another value -> 4 in the result list??? > > ----------------------------------------- > SELECT T1.ID,T2.ID,T3.ID > FROM TEST_3 T3,TEST_2 T2, TEST_1 T1 > WHERE T3.ID = T1.ID AND T1.ID = T2.ID(+) > > Result: > 1,1,1 > 2,2,2 > 3,3,3 > 4,NULL,NULL > ----------------------------------------- > > I also made this test with an old AdabasD DB and it was no > problem - 3 > Results for both SELECTs. > > So, it seems to be a bug in MaxDB, isn't it?
Hi, you are right it's a bug and we are working on it. As a workaround you could enable new outer join handling via command "diagnose optimize join outer on". Thanks for reporting it. Kind regards, Holger -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
