Practical
Issues in Database Management Errata |
|||
Page
|
Location
|
Correction
|
|
10
|
Line 15 | "DATE" should be "YEAR" | |
51
|
SQL statement |
T5: NOT
|
(r2.res# <> r1.res#
AND r2.room = r1.room AND r2.arr_date < r1.dpt_date AND r2.dpt_date > r1.arr_date) |
53-54
|
SQL statement | All instances of "OR" should be "AND" | |
54
|
SQL statement |
NOT
|
(r2.res# <> r1.res# AND r2.room = r1.room AND r2.arr_date < r1.dpt_date AND r2.dpt_date > r1.arr_date) |
89
|
Line 1 | "MGR" should be "MGR#" | |
89
|
SQL statement | "mgr" should be "mgr#" | |
98
|
Line 25 | "Figure 4.4" should be "Figure 4.3" | |
106
|
Reference [3] | Should read: C.J. Date, "Why Duplicate Rows Are Prohibited," Relational Database Writings 1985-1989, Reading, MA: Addison-Wesley, 1995. | |
138
|
Table A in Figure 5.8 | ![]() |
|
140
|
Table A in Figure 5.9 | ![]() |
|
161
|
Extract, line 4 | "[EMP]" should be "[EMPLOYEES]" | |
189
|
Figure 8.3 | ![]() |
|
195
|
Section 8.2.4, line 2 | "PROJECT" should be "PROJ", "ACTIVITY" should be "ACT" | |
195
|
Figure 8.8 | ![]() |
|
196
|
Diagram after first paragraph of text | ![]() |
|
197
|
Figure 8.9 | ![]() |
|
201
|
Two comparisons at top of page | All instances of "project" should be "proj"; all instances of "activity" should be "act". | |
203
|
SQL statement | "project" should be" proj"; "activity" should be "act" | |
204
|
SQL statement | All instances of "project" should be "proj"; all instances of "activity" should be "act". | |
232
|
Line 9 | "redundancy" should be "missing values" | |
235
|
Figure 10.8 | ![]() |
|
236
|
Last paragraph, line 1 | "facts" should be "values" |