Errata

Oracle Design: The Definitive Guide

Errata for Oracle Design: The Definitive Guide

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page 78
para. 3, line 2

"is for a blue Ghia but she does not mind which model"

now reads

"is for a blue Ghia but she does not mind which car"

(change "model" to "car")

Also, the code sample has been changed to:

SELECT cml.car_name
FROM model_color_links mcl
, car_model_links cml
WHERE mcl.model_name = cml.model_name
AND mcl.color_name = 'Blue'
AND cml.model_name = 'GL'

Anonymous    Jan 01, 1999
Printed
Page 79
Figure 3-16 is new

Anonymous    Sep 01, 1997
Printed
Page 80
Figure 3-17: The boxes for "DEPARTMENT" and "EMPLOYMENT" have

been switched.

Anonymous    Aug 01, 1999
Printed
Page 81
Figure 3-18: The relationship shown is reversed.

The words "mananged by" and "the manager of" have been switched.

Anonymous    Aug 01, 1999
Printed
Page 81
in the first complete sentence (lines 1-3)

"In other words, the subtypes must be mutually exclusive, and
there cannot be any occurances of the subtype which do not
belong to a subtype."

the last word now reads "supertype" rather than "subtype"

Anonymous    Aug 01, 1999
Printed
Page 120
2nd para. in box: changed "'ab,'" to "'ab '"

Anonymous    Sep 01, 1997
Printed
Page 127

last code example on the page now reads:

SELECT *
FROM t
WHERE NVL(:p, '$NULL') = NVL(t.a,'$NULL');

Anonymous    Sep 01, 1997
Printed
Page 174
line 18 of examble 1b

Line 19

IF p_from <= SYSDATE

should be:

IF p_from > SYSDATE

Anonymous   
Printed
Page 220
replaced the three bullet items with the following

* For each tablespace, always set PCTINCREASE to zero, because any
other value is liable to cause tablespace free space fragmentation.

* For each tablespace, set the values of INITIAL and NEXT equal to each
other.

* For objects within a tablespace, do not ordinarily specify the
INITIAL, NEXT, or PCTINCREASE values (allow them to be inherited from
the tablespace).

Anonymous    Sep 01, 1998
Printed
Page 222
In the fourth paragraph, the text states

"If PCTFREE and PCTFREE are too close together..."

Should be "If PCTFREE and PCTUSED are too close together..."

Anonymous   
Printed
Page 528
added the following to the next-to-last para.

Whenever possible, our books use RepKover (tm), a durable and flexible
lay-flat binding. If the page count exceeds RepKover's limit, perfect
binding is used.

Anonymous    Mar 01, 1998