Hi, it seems to be a problem with the replication of the error message from our inhouse system to the public system.
The responsible colleagues will check this. The bug is still in process and have to be fixed with one of the next releases. Kind regards, Holger SAP Labs Berlin > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 27. Januar 2004 23:59 > To: Becker, Holger; [EMAIL PROTECTED] > Subject: RE: SQL Bug? > > > The link on this bug CR no longer works. I thought that meant > it would be > fixed in the new release v 7.4.3.31 but it is not fixed. Can > you please > let me know if the change request still active or did the dev > team think > they fixed it in 7.4.3.31 and deleted the CR# as a result. > > Thanks, > > Josh Ralph > > > > > > > "Becker, Holger" <[EMAIL PROTECTED]> > 01/09/2004 12:38 AM > > > To: "'[EMAIL PROTECTED]'" > <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > cc: > Subject: RE: SQL Bug? > > > [EMAIL PROTECTED] wrote: > > > I am running a query using the Oracle & Internal SQL modes > on version > > 7.4.3.30 that should return results, but it is not. Below is > > an example. > > Is this a bug or intentional? If it is intentional, can you > > please give me > > an explaination why it works this way. Thanks for you time. > > > > Here are the table DDL and insert statements for the example. > > The example > > assumes you have a schema named EXAMPLE > > > > ... > > > > This is the SQL statement that does not return results. > > SELECT * > > FROM EXAMPLE.M1, EXAMPLE.M2, EXAMPLE.S > > WHERE M1.OID_M1 = M2.OID_M1 > > AND M1.OID_S = S.OID_S(+) > > AND M1.FLAG_DEL <> 'T' > > AND M2.FLAG_DEL <> 'T' > > > > Below are several variations of the same query that do > > produce the results > > I expect. > > SELECT * > > FROM EXAMPLE.M1, EXAMPLE.M2, EXAMPLE.S > > WHERE M1.OID_M1 = M2.OID_M1 > > AND M1.OID_S = S.OID_S(+) > > AND M2.FLAG_DEL <> 'T' > > AND M1.FLAG_DEL <> 'T' > > > > ... > > It's a bug and it seems that it's new with version >= 7.4 > because in 7.3 it works as expected. > > I'm still analyzing the problem but we'll fix it one of the > next versions no shedule by no but you could check > http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1126980 > for ongoing information. > > Thank you for reporting it. > > Kind regards, > Holger > SAP Labs Berlin > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
