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.
| Version |
Location |
Description |
Submitted By |
Date Submitted |
Date Corrected |
| Printed |
Page 16
Paragraph 5, clause between em-dashes |
The clause in the paragraph that is set off by em-dashes currently reads as follows:
--in effect, you can think of a base relation as being dynamically built--
The word "as" was inadvertently added to the sentence during proofreading.
Unfortunately, the added word renders the sense of the sentence incorrect. The sentence should instead
read:
--in effect, you can think of a base relation being dynamically built--
In Chris's own words: "I was trying to emphasize the fact that (as the first part of
the sentence containing the quoted text actually says) you can operate on views <i>as
if they were</i> base relations."
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
16
Paragraph 5, clause between em-dashes |
The clause in the paragraph that is set off by em-dashes currently reads as follows:
--in effect, you can think of a base relation as being dynamically built--
The word "as" was inadvertently added to the sentence during proofreading.
Unfortunately, the added word renders the sense of the sentence incorrect. The sentence should instead
read:
--in effect, you can think of a base relation being dynamically built--
In Chris's own words: "I was trying to emphasize the fact that (as the first part of
the sentence containing the quoted text actually says) you can operate on views <i>as
if they were</i> base relations."
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 21
In Safari: Exercise 1-8 |
Typo:
Figures Figures 1-1 and 1-3
should read
Figures 1-1 and 1-3
|
Anonymous |
|
|
| Printed |
Page 43
middle of the page |
(but the order in which the attributes is specified is arbitrary)
should read
(but the order in which the attributes are specified is arbitrary)
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
43
middle of the page |
(but the order in which the attributes is specified is arbitrary)
should read
(but the order in which the attributes are specified is arbitrary)
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 76
line 5 |
Replace:
"projection well"
with
"projection ... well"
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
76
line 5 |
Replace:
"projection well"
with
"projection ... well"
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 106
3rd paragraph (after 2nd code snippet) |
"apart from this one rather special one."
should read
"apart from this rather special one."
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
106
3rd paragraph (after 2nd code snippet) |
"apart from this one rather special one."
should read
"apart from this rather special one."
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 107
last example |
The current last two lines of the expression should be replaced with:
R2 { ALL BUT WEIGHT, CITY } AS R3,
R3 RENAME { NEW_WEIGHT AS WEIGHT, NEW_CITY AS CITY } AS R4,
P MINUS R1 AS R5 :
R5 UNION R4;
In the paragraph immediately following, the sentence beginning "Finally" should read as follows:
Finally, we rename NEW_WEIGHT and NEW_CITY as WEIGHT and CITY,
respectively (that's R4); then we identify the set of tuples not to be
updated (that's R5), and assign the union of R5 and R4 to relvar P.
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
107
last example |
The current last two lines of the expression should be replaced with:
R2 { ALL BUT WEIGHT, CITY } AS R3,
R3 RENAME { NEW_WEIGHT AS WEIGHT, NEW_CITY AS CITY } AS R4,
P MINUS R1 AS R5 :
R5 UNION R4;
In the paragraph immediately following, the sentence beginning "Finally" should read as follows:
Finally, we rename NEW_WEIGHT and NEW_CITY as WEIGHT and CITY,
respectively (that's R4); then we identify the set of tuples not to be
updated (that's R5), and assign the union of R5 and R4 to relvar P.
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 109
5.9 2nd paragraph |
On Safari only:
If one supplier has CITY value 'Paris' and Paris 'another ',
should read:
If one supplier has CITY value 'Paris' and another 'Paris ',
|
Anonymous |
|
|
| Printed |
Page 115
6.0 1st paragraph |
On Safari only:
... in preceding chap ters
should read
... in preceding chapters
and all words should be bold.
|
Anonymous |
|
|
| Printed |
Page 145
7.3.1 1st paragraph |
(and so could be nonloss-decomposed to adavantage).
should read
(and so could be nonloss-decomposed to advantage).
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
145
7.3.1 1st paragraph |
(and so could be nonloss-decomposed to adavantage).
should read
(and so could be nonloss-decomposed to advantage).
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 147
; Sentence immediately following the definition of 6NF |
Equivalently, a "regular" relvar is in 6NF if and only if it consists of a single key, plus at most one
additional attribute.
should be:
Note in particular that a "regular" relvar is in 6NF if it consists of a single key, plus at most one
additional attribute.
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
147
; Sentence immediately following the definition of 6NF |
Equivalently, a "regular" relvar is in 6NF if and only if it consists of a single key, plus at most one
additional attribute.
should be:
Note in particular that a "regular" relvar is in 6NF if it consists of a single key, plus at most one
additional attribute.
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 161
ExercIse 7-23 |
On Safari only:
Modified version of Exercises 7-27
should read
Modified version of Exercise 7-21
|
Anonymous |
|
|
| Printed |
Page 162
ExercIse 7-26 |
On Safari only:
from Exercises 7-11 , 7-14 7-21 , and 7-23
should read
from Exercises 7-11 , 7-14, 7-21 , and 7-23
|
Anonymous |
|
|
| Printed |
Page 167
2nd paragraph after "Relational Operators" |
"Now, there seems to a widespread misconception concerning"
should read
"Now, there seems to be a widespread misconception concerning"
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
167
2nd paragraph after "Relational Operators" |
"Now, there seems to a widespread misconception concerning"
should read
"Now, there seems to be a widespread misconception concerning"
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 195
Example 8 |
s.SNO, COUNT ( sp WHERE sp.PNO = s.SNO ) AS P_COUNT
should read
s.SNO, COUNT ( sp WHERE sp.SNO = s.SNO ) AS P_COUNT
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
195
Example 8 |
s.SNO, COUNT ( sp WHERE sp.PNO = s.SNO ) AS P_COUNT
should read
s.SNO, COUNT ( sp WHERE sp.SNO = s.SNO ) AS P_COUNT
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 196
Abraham Lincoln quote |
Quote is incorrect!
Correct quote is:
"You can fool some of the people all of the time, and all of the people some of the
time, but you can not fool all of the people all of the time."
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
196
Abraham Lincoln quote |
Quote is incorrect!
Correct quote is:
"You can fool some of the people all of the time, and all of the people some of the
time, but you can not fool all of the people all of the time."
|
Anonymous |
|
May 01, 2008 |
| Printed |
Page 207
Index T: THE_ operator |
Reference to page 27 in the index should be to page 28.
|
Anonymous |
|
May 01, 2008 |
| Other Digital Version |
207
Index T: THE_ operator |
Reference to page 27 in the index should be to page 28.
|
Anonymous |
|
May 01, 2008 |
