|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
RE: ROWNO & outer joins - possible bug
From: Becker, Holger (holger.becker
sap.com)
Date: Fri Jul 08 2005 - 08:40:35 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marcin P wrote:
> Hello,
> I think I've found a bug with ROWNO in WHERE clause -
> it doesn't work as expected.
> Here is a sample script:
>
> CREATE TABLE "TALD_ADMIN"."TBLTEST_ASSETS"
> (
> "REC_ID" Fixed (15,0) NOT NULL,
> "INVENTORY_NO" Varchar (50) ASCII,
> "IMPORT_OP_ID" Integer,
> PRIMARY KEY ("REC_ID")
> )
> //
> CREATE TABLE "TALD_ADMIN"."TBLTEST_OPERATIONS"
> (
> "REC_ID" Fixed (15,0) NOT NULL,
> "OPERATION_ID" Integer,
> "OPERATION_TYPE" Varchar (50) ASCII,
> PRIMARY KEY ("REC_ID")
> )
> //
> INSERT INTO "TALD_ADMIN"."TBLTEST_OPERATIONS"
> VALUES(1,1,'Import')
> //
> INSERT INTO "TALD_ADMIN"."TBLTEST_OPERATIONS"
> VALUES(2,2,'Acceptation')
> //
> INSERT INTO "TALD_ADMIN"."TBLTEST_ASSETS"
> VALUES(1,'A0001',NULL)
> //
> INSERT INTO "TALD_ADMIN"."TBLTEST_ASSETS"
> VALUES(2,'A0002',1)
> //
> INSERT INTO "TALD_ADMIN"."TBLTEST_ASSETS"
> VALUES(3,'A0003',2)
> //
> CREATE VIEW DBVTEST_ASSETS_OPERATIONS AS
> SELECT A.REC_ID, A.INVENTORY_NO, OP_I.OPERATION_TYPE AS I_OP_TYPE
> FROM TBLTEST_ASSETS A, TBLTEST_OPERATIONS OP_I
> WHERE OP_I.OPERATION_ID(+)=A.IMPORT_OP_ID
>
> And here are the test queries:
>
> // 2 rows expected - 2 rows selected -> OK
> SELECT *, ROWNO FROM TBLTEST_ASSETS WHERE ROWNO <= 2
> //
> // 2 rows expected - 3 rows selected -> ERROR
> SELECT *, ROWNO FROM DBVTEST_ASSETS_OPERATIONS WHERE ROWNO <= 2
>
> Could anyone try to reproduce it?
> I use MaxDB 7.5.0.16.
>
Hi,
yes I could reproduce this problem also with the newest version of
MaxDB.
It's a bug in outer join handling for joins without index or key
transitions.
We'll fix it with one of the next release.
For detailed progress information have a look here
http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1136687
Thank you for reporting this bug and sorry for any inconvenience.
Kind regards
Holger
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]