Dirk Naujoks wrote: > We have a sql-statement simmilar to the following > > select "username"."table1name".*, "username"."table2name".*, > "username"."table3name".* > from "username"."table1name" inner join "username"."table2name" > on "username"."table1name".idfeld="username"."table2name".idfeld > outer join "username"."table3name" on ( > "username"."table1name".idfeld="username"."table3name".idfeld > and > "username"."table3name".feld2 = 2005 > and > "username"."table3name".feld3 = '6707*) > where foo1=x > and foo2=y > > > After upgrading to version 7.5.00.31 we get the error message > "Outer join not allowed in this context". > > Changing the statement to (remove owner) > either > select "table1name".*, "table2name".*, "table3name".* > from "table1name" inner join "table2name" > on "table1name".idfeld="table2name".idfeld > outer join "table3name" on ( > "table1name".idfeld="table3name".idfeld > and "table3name".feld2 = 2005 > and "table3name".feld3 = '6707*) > where foo1=x > and foo2=y > > or (using an alias) > > select t1.*, t2.*, t2.* > from "username"."table1name" t1 inner join "username"."table2name" t2 > on t1.idfeld=t2.idfeld > outer join "username"."table3name" t3 on ( t1.idfeld=t3.idfeld > and t3.feld2 = 2005 > and t3.feld3 = '6707*) > where foo1=x > and foo2=y > > has the result, that the error message doesn't appear. > > We need to use the username (schemaname) in the statement. > > What is the reason for this behaviour. The documentation says > that it is > an error using values in the outer join statement. > > Dirk Naujoks
Hi, this is a bug in outer join handling in MaxDB. We will fix it with one of the next releases. For detailed information about target version have a look at http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1139306. Thank you for reporting this bug. Kind regards Holger -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
