Errata

The query and the results do not match (the book shows results ordered by city).


QUERY IN THE BOOK:
===================

SELECT c.first_name, c.last_name, ct.city
FROM customer AS c
INNER JOIN address AS a
ON c.address_id = a.address_id
INNER JOIN city AS ct
ON a.city_id = ct.city_id;


SHOULD BE:
============

SELECT c.first_name, c.last_name, ct.city
FROM customer AS c
INNER JOIN address AS a
ON c.address_id = a.address_id
INNER JOIN city AS ct
ON a.city_id = ct.city_id
ORDER BY ct.city;

In the Kindle version:

The following query returns 54 rows:

SELECT f.title
-> FROM film f
-> INNER JOIN film_actor fa
-> ON f.film_id = fa.film_id
-> INNER JOIN actor a
-> ON fa.actor_id = a.actor_id
-> WHERE ((a.first_name = 'CATE' AND a.last_name = 'MCQUEEN')
-> OR (a.first_name = 'CUBA' AND a.last_name = 'BIRCH'));

The text "Between them, the two actors appeared in 52 different films...",
should be "Between them, the two actors appeared in 54 different films..."

I believe there is a typo in the description of the negation of the OR statement used in the example:

WHERE NOT (first_name = 'STEVEN' OR last_name = 'YOUNG')
AND create_date > '2006-01-01'

In the sentence below, "or" should be replaced by "and":
"I am retrieving only rows where the first name is not Steven or the last name is not Young whose record was created after January 1, 2006."

The example query at the bottom of page 49 uses aliases "language_usage", "lang_pi_value", and "language_name" without explaining that they are aliases.

I believe this is a typo and that the column aliases should not have been used in this query on page 49. Because, on page 50, the same query is repeated and it is explained you can add column labels to the result set by adding the column alias after each column in the query.

Suggested fix: Modify the query and its result set table on page 49 to remove the use of column aliases.

Type SELECT CHAR(97,98,99,100,101,102,103); retrieves in hexadecimal form:
+---------+----------------------------------------------------------------+
| abcdefg | CHAR(97,98,99,100,101,102,103) |
+---------+----------------------------------------------------------------+
| abcdefg | 0x61626364656667 |
+---------+----------------------------------------------------------------+
Since using s\; command in line shows:
...Binary data as: Hexadecimal...

And using the MySQL documentation:
mysql> SELECT CHAR(128,129,130,131 USING utf8mb4);
+-------------------------------------+
| CHAR(128,129,130,131 USING utf8mb4) |
+-------------------------------------+
| |
+-------------------------------------+
1 row in set, 1 warning (0.01 sec)

The example in the book does not match.

There is a typo in the second bullet point of foreign key constraints.
It should be "on delete cascade", instead of "on update cascade".