Errata

The text says that NOT is an operator being applied to the IN operator to perform a
NOT IN operation. Strictly speaking, the NOT operator applies to expressions, not to
other operators. NOT IN is an operator, distinct from IN, just like <> and != are
distinct operators that perform the opposite operation of =. (It's just one that
happens to be composed of two keywords.)

The IN and NOT operators are actually being used if you say NOT A IN (X, Y, Z).
Saying A NOT IN (X, Y, Z) is using a different but complementary operator that
happens to flow better to English speakers

If the NOT operator also operated on other operators, then you could say WHERE A NOT
= B, but you can't--you'll get the error "ORA-00920: invalid relational operator" if
you try that.

The same discussion applies to BETWEEN vs. NOT BETWEEN at the top of page 21, first
paragraph.

It also holds for LIKE vs. NOT LIKE on page 21, 7th paragraph, beginning "For this
pattern".

It also holds for IS NULL vs. IS NOT NULL on page 22, paragraph 4.

In a similar vein, on page 22, paragraph 2, it claims the existence of an IS
operator. IS NULL is the entire operator--and IS NOT NULL is a distinct but
complementary operator, one comprised of three keywords.

NOW READS:
SELECT P.NAME PART_NAME, C.INV_CLASS INV_CLASS

NOW READS:
SELECT E.LNAME EMPLOYEE, M.NAME MANAGER

All the queries in this section should refer to the DEPT view instead of the
DEPARTMENT table.

CREATE OR REPLACE VIEW V_RTLR_EMP AS
SELECT C.RTLR_NBR, C.NAME, C.CITY, E.EMP_ID, E.LNAME SALES_REP
FROM RETAILER C, EMPLOYEE E
WHERE C.SALESPERSON_ID = E.EMP_ID;

NOW READS:
CREATE OR REPLACE VIEW V_RTLR_EMP AS
SELECT C.RTLR_NBR, C.NAME, C.CITY, E.EMP_ID, C.SALESPERSON_ID, E.LNAME SALES_REP
FROM RETAILER C, EMPLOYEE E
WHERE C.SALESPERSON_ID = E.EMP_ID;

In the last two example queries,
HAVING COUNT(ORDER_NBR) > 1

NOW READS:
HAVING COUNT(ORDER_NBR) > 2

The result sets in the text did not reflect the published data.

Result set NOW READS:

DEPT_ID NAME TOT
---------- -------------------- ----------
1 Human Resources 1
2 Accounting 1
3 Domestic Sales 19
4 International Sales 5

The result sets in the text did not reflect the published data.

Result set NOW READS:

DEPT_ID DEPT_NAME TOT_ORDERS
---------- -------------------- ----------
3 Domestic Sales 666
4 International Sales 175

The result sets in the text did not reflect the published data.

Result set NOW READS:

SALES_EMP_ID TOT_ORDERS
------------ ----------
11 35
12 35
13 35
14 35
15 35
16 35
17 35
18 35
19 35
20 35
21 35
22 35
23 35
24 35
25 35
26 35
27 35
28 35
29 35
30 36
31 35
32 35
33 35
34 35

The result sets in the text did not reflect the published data.

The first result NOW READS:

DEPT_ID TOT_ORDERS
---------- ----------
3 666

4 175

The result sets in the text did not reflect the published data.

The second result set NOW READS:

DEPT_ID DEPT_NAME TOT_ORDERS
---------- -------------------- ----------
3 Domestic Sales 666
4 International Sales 175

Figure 8-2 shows the wrong columns names for the EMPLOYEE table. The correct column
names are: EMP_ID, FNAME, LNAME, DEPT_ID, MANAGER_EMP_ID, SALARY, HIRE_DATE, and
JOB_ID. The figure does, however, correctly illustrate the concept that the EMPLOYEE
table refers back to itself (via the MANAGER_EMP_ID column).

The result sets in the text did not reflect the published data.

In the two result sets,
The number 2975 NOW READS 2000
The date 01-MAY-81 NOW READS 01-MAY-80

The result sets in the text did not reflect the published data.

In the two examples,
The number 10875 NOW READS 9900
The number 29025 NOW READS 28050

Oracle8i vs Oracle9i Differences

1. Sequence of returned rows:

When the same query is executed in Oracle8i and Oracle9i,
the sequence of rows in the result set could be different.
There could be differences in the sequence of rows returned
from a Oracle9i Release 1 database and Oracle9i Release 2 database.

2. Slight syntax difference:

The following syntax works in 8i, but not in 9i:

SELECT O.YEAR, TO_CHAR(TO_DATE(O.MONTH, 'MM'), 'Month') MONTH,
R.NAME REGION, SUM(O.TOT_SALES)
FROM ORDERS O, REGION R
WHERE R.REGION_ID = O.REGION_ID
AND O.MONTH BETWEEN 1 AND 3
GROUP BY O.YEAR, O.MONTH ROLLUP (R.NAME);

Oracle9i expects a comma(,) between O.MONTH and ROLLUP in the last line.
Oracle8i is fine with or without the comma.

The following syntax works well in both 8i and 9i:

SELECT O.YEAR, TO_CHAR(TO_DATE(O.MONTH, 'MM'), 'Month') MONTH,
R.NAME REGION, SUM(O.TOT_SALES)
FROM ORDERS O, REGION R
WHERE R.REGION_ID = O.REGION_ID
AND O.MONTH BETWEEN 1 AND 3
GROUP BY O.YEAR, O.MONTH, ROLLUP (R.NAME);

The WHERE clause NOW READS:
WHERE R.REGION_ID = O.REGION_ID AND YEAR = 2001

All the WHERE clauses NOW READ:
WHERE R.REGION_ID = O.REGION_ID AND YEAR = 2001

The WHERE clause NOW READS:
WHERE R.REGION_ID = O.REGION_ID AND YEAR = 2001

The WHERE clause NOW READS:
WHERE R.REGION_ID = O.REGION_ID AND YEAR = 2001

the ranges for each bucket will be 1 to 1,000,000, 1000,0001 to 2,000,000, and 2,000,0001 to 3,000,000.

NOW READS:
the ranges for each bucket will be 1 to 1,000,000, 1000,001 to 2,000,000, and 2,000,001 to 3,000,000.