Oracle 9.2.0.1 query bug?

Question

The following test case gives different results on Oracle 9.2.0.1 and 10g. 10g and 3 other competing database products give the answer as
FILES_ID VIEW1_ID VIEW2_ID
1 1 1
while Oracle 9.2.0.1 yields
FILES_ID VIEW1_ID VIEW2_ID
1 1 1
2
The test case is
CREATE TABLE FILES (ID INTEGER);
CREATE TABLE PROPERTIES (ID INTEGER, VERSION INTEGER);
INSERT INTO FILES VALUES (1);
INSERT INTO FILES VALUES (2);
INSERT INTO PROPERTIES VALUES (1, 1);
SELECT FILES.ID AS FILES_ID,
VIEW1.ID AS VIEW1_ID,
VIEW2.ID AS VIEW2_ID
FROM FILES
LEFT OUTER JOIN
(SELECT ID, VERSION FROM PROPERTIES) VIEW1
ON (VIEW1.ID = FILES.ID AND
(VIEW1.VERSION = 1 OR VIEW1.VERSION = -1))
LEFT OUTER JOIN
(SELECT ID, VERSION FROM PROPERTIES) VIEW2
ON (VIEW2.ID = FILES.ID AND
(VIEW2.VERSION = 1 OR VIEW2.VERSION = -1))
WHERE
(FILES.ID = 1 OR FILES.ID = 2) AND
((VIEW1.ID = FILES.ID AND FILES.ID = 1) OR
(VIEW2.ID = FILES.ID AND FILES.ID = 1));
DROP TABLE FILES;
DROP TABLE PROPERTIES;
First, I may be doing something silly but it seems odd that 9 and 10 give me different answers. I don't have access to Oracle support, so I don't know if a more recent patch of 9 would give the seemingly-correct 10g answer. Would anyone who has access to a recent 9.2.x version please try this?
Ideally I need to know what 9.2.x patch this was fixed in so I known the minimum version or Oracle required for my product.
Thanks

Answer 1

Well 9.2.0.1 is six patches out of date. I don't know when this was fixed but...
SQL*Plus: Release 9.2.0.6.0 - Production on Mon Oct 10 17:09:17 2005
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
SQL> CREATE TABLE FILES (ID INTEGER);
Table created.
SQL> CREATE TABLE PROPERTIES (ID INTEGER, VERSION INTEGER);
Table created.
SQL> INSERT INTO FILES VALUES (1);
1 row created.
SQL> INSERT INTO FILES VALUES (2);
1 row created.
SQL> INSERT INTO PROPERTIES VALUES (1, 1);
1 row created.
SQL> SELECT FILES.ID AS FILES_ID,
  2  VIEW1.ID AS VIEW1_ID,
  3  VIEW2.ID AS VIEW2_ID
  4  FROM FILES
  5  LEFT OUTER JOIN
  6  (SELECT ID, VERSION FROM PROPERTIES) VIEW1
  7  ON (VIEW1.ID = FILES.ID AND
  8  (VIEW1.VERSION = 1 OR VIEW1.VERSION = -1))
  9  LEFT OUTER JOIN
10  (SELECT ID, VERSION FROM PROPERTIES) VIEW2
11  ON (VIEW2.ID = FILES.ID AND
12  (VIEW2.VERSION = 1 OR VIEW2.VERSION = -1))
13  WHERE
14  (FILES.ID = 1 OR FILES.ID = 2) AND
15  ((VIEW1.ID = FILES.ID AND FILES.ID = 1) OR
16  (VIEW2.ID = FILES.ID AND FILES.ID = 1));
  FILES_ID   VIEW1_ID   VIEW2_ID
         1          1          1
SQL>
but it seems odd that 9 and 10 give me different answersFnord. If there's a bug in one version of the database it's silly that they don't port it to new versions but fix it instead?
Cheers, APC