Errata

Says MySQL -- The book is not a MySQL book.

Says MySQL -- The book is not a MySQL book.

.... (as shown in Figures 1-26 and 1-28 of Chapter 1).
Should be Figures 1-25 and 1-27 respectively.

Whole paragraph is incorrect becuase actions cannot be performed that are being asked. Right clicking on the table does
not give the option to click "Columns" as specified.

Expanding the Table and then expanding Columns sub-node will show the column definitions for that table. Right clicking
on the table and selecting Design will also show the column definitions.

The screen shot displays a KEY symbol for the PNO field. The table has no keys assigned at this point in the book.

The book states: "The only field in the Dependent table that cannot be null is
STNO."

The dependent table does not have an STNO column (field). STNO should be PNO.

Also in Figure 2-1, there is no explanation of what PK means in the PNO field. While
this is probably covered in later chapters, everything else in that figure is
explained in the text above but that single item.

Table1.FieldA should be TableA.Field1

Unless you know which numbers in the student table class column refer to Sophomores, juniors or seniors this exercise
cannot be accomplished properly. Being British I had never come across the term Sophomores before and had to look it up
to know it meant 2nd grade or 2 in the student table class column.

In question 2.b on pg. 103, it suggests that the table T2 must have different descriptions for each row. For the
following:

T1
---
'Bob', 1
'Sam', 2
'Bill', 3

T2
---
2, 'Desc 2'
2, 'Desc 2'

use Student_course
select * from T1 t1, T2 t2
where t1.jobno = t2.jobno

I get the following results:

name jobno jobno jobdesc
-------------------- ----------- ----------- --------------------
Sam 2 2 Desc 2
Sam 2 2 Desc 2

(2 row(s) affected)

Why does the question suggest that the rows have to contain different descriptions? Unless there is some restriction from
entering duplicate rows for table T2 (which there is not), I would expect to get one row for each match for the equi-join
performed in question 2.a.

Table Employee has the Salary Column instead of Wage.

From the preceding chapters, there doesn't appear to be instruction concerning how to achieve the numbering of rows to
achieve PERSON # 1, 2, 3, 4, etc.

There doesn't appear to be instruction by this point in the book about how to achieve printing the number of courses by
each instructor or classes by each student. This can be done with a GROUP BY clause, but this hasn't been introduced yet.

In the section on using column aliases when creating Views, it states on pg. 162 that the name of the view has to precede
the column alias as in:

SELECT namemaj2.[name], namemaj2.[maj]
FROM namemaj2
WHERE namemaj2.[name] LIKE 'J%'

Because it seems completely nonintuitive to require knowledge about which column names are aliases, I also tried the
following which works and would seem to be the more normal usage:

select name, maj
from namemaj2
where name like 'J%'

The select statement presented in the book filters on course_name rather than course_num. Technically, this misses any
accounting classes not starting with 'ACC'. For example, the class "Managerial Finance" is considered an accounting
class. Filtering on course_num LIKE 'ACC%' gives you 29 rows.

The paragraph says we can see that the empno and title fields will not allow nulls, but the "Allow Nulls" box is checked
for "title." This is the same result I got when I ran the code. The first bullet claims "UNIQUE does not necessitate NOT
NULL." It seems the paragraph below Figure 11-13 should be revised.