Errata

Last sentence of paragraph 2, says "bu the rest is the same." I think it should state "but the rest is the same."

30 years > 20 years

THERE ARE NO PAGE NUMBERS GIVEN IN SAFARI BOOKS PRESNENTATION OF THE BOOK.

At Chapter 5 -- Altering Tables
Topic: "Essential Changes"
About 70% through the topic.

Within the paragraph beginning "To set the values in a column that has an enumerated list ..." we are later told:

"For instance, you could do an UPDATE statement like this to set all birds in the table to Lower Risk - Least Concern, the seventh value:

UPDATE birds_new
SET endangered = 7 ;"

However, a review and inspection of the prior guidance shows that the ENUM data type declaration specified EIGHT values for endangered:

ALTER TABLE birds_new
-> MODIFY COLUMN endangered
-> ENUM('Extinct',
-> 'Extinct in Wild',
-> 'Threatened - Critically Endangered',
-> 'Threatened - Endangered',
-> 'Threatened - Vulnerable',
-> 'Lower Risk - Conservation Dependent',
-> 'Lower Risk - Near Threatened',
-> 'Lower Risk - Least Concern')
-> AFTER family_id ;

The SEVENTH of these values was 'Lower Risk - Near Threatened',
while the EIGHTH value was 'Lower Risk - Least Concern'.

Setting the value for endangered to 7 as directed should yield the enumerated endangered indication of 'Lower Risk - Near Threatened',
rather than 'Lower Risk - Least Concern'.

To set the value to 'Lower Risk - Least Concern', readers should specify this MySQL:

UPDATE birds_new
SET endangered = 8 ;

Thanks!

THERE ARE NO PAGE NUMBERS GIVEN IN SAFARI BOOKS PRESNENTATION OF THE BOOK.

At Chapter 5 -- Altering Tables
Topic: "Optional Changes - Setting a Column's Default Value"
About 25% through the topic.

Within the paragraph beginning "We named the reference table conservation_status ...", the last sentence reads:

"We'll put Lower Risk in the conservation_category column and Least Concern in another column called, conservation_category."

It is clear that it is intended to describe two different fields and from context the sentence should probably read:

"We'll put Lower Risk in the conservation_category column and Least Concern in another column called, conservation_state."

* * * * *

This might be the same errata item noted by Anonymous on Oct 18, 2016 as appearing on Page 72 of the print edition.

THERE ARE NO PAGE NUMBERS GIVEN IN SAFARI BOOKS PRESNENTATION OF THE BOOK.

At Chapter 5 -- Altering Tables
Topic: "Optional Changes - Setting a Column's Default Value"
About 60% through the topic.

There appears a paragraph which begins with these two sentences:

"Notice that we have been prefixing the table name with the database name (i.e. rookery.conservation_status). That's because we had set the default database to test with USE."

It is TRUE that we had been using a different database than rookery. However, UNLESS the reader SKIPPED the section on "Dynamic Columns," the most recent USE statement was "USE birdwatchers" rather than "USE test."

* * *

The LAST USE statement seems to have been set within the "Dynamic Columns" subtopic in the Topic "Essential Changes" in Chapter 5 ("Altering Tables):

USE birdwatchers;

This is shown about 75% of the way through the Topic "Essential Changes."

* * * * *

This is a rather persnickety typo, but probably should be corrected in a future edition.

Thanks!

THERE ARE NO PAGE NUMBERS GIVEN IN SAFARI BOOKS PRESNENTATION OF THE BOOK.

At Chapter 5 -- Altering Tables
Topic: "Optional Changes - Another Method to Alter and Create a Table"
About 55% through the topic.

In yet another instance of an inconsistency which causes confusion and distraction, we are given inconsistent information regarding the correct AUTO-INCREMENT value for table birds.

This text appears within the book:

"In this excerpt of the results, you can see that the variable, AUTO_INCREMENT is currently 6. Set AUTO_INCREMENT to the same value in the birds_new table by entering the following SQL statement in MySQL:

ALTER TABLE birds_new
AUTO_INCREMENT = 6 ; "

However, if one actually checks the value, the value is set to 10. This is because it was previously MANUALLY CHANGED in the prior lesson.

* * *

Within the immediate preceding topic "Setting the Value of AUTO_INCREMENT" the reader is instructed:

"Enter the following in MySQL:

USE rookery

ALTER TABLE birds
AUTO_INCREMENT = 10 ;

This will cause the bird_id to be set to 10 for the next row of data on a bird that we enter into the birds table."

If the reader follows this instruction, the the value of AUTO_INCREMENT will be 10 rather than 7 as erroneously shown in the subsequent section.

* * * * *

Thanks!

NOTE: THE SAFARI BOOKS ONLINE PRESENTATION OF THE BOOK Learning MySQL and MariaDB DOES NOT CONTAIN PAGE NUMBERS.

Chapter 6 - Inserting Data
Topic: "Practical Examples - The Table for Bird Families"
The issue begins about 20% through this section with the treatment by the server of the suggested MySQL client statement:

INSERT INTO bird_families
-> VALUES ('Anatidae', "This family includes ducks, geese and swans.", NULL, 103) ;

The book indicates that the user will get a Warning message, but that the data will be entered into the bird_families table.

I received a different result, an ERROR message and the presented row DID NOT TAKE AT ALL:

MariaDB [rookery]> INSERT INTO bird_families
-> VALUES ('Anatidae', "This family includes ducks, geese and swans.", NULL,
103) ;
ERROR 1366 (22007): Incorrect integer value: 'Anatidae' for column 'family_id' at row 1

I DID also seek to verify the warning and received this response:

MariaDB [rookery]> SHOW WARNINGS \G
*************************** 1. row ***************************
Level: Error
Code: 1366
Message: Incorrect integer value: 'Anatidae' for column 'family_id' at row 1
1 row in set (0.00 sec)

* * * * *

I am using MariaDB Ver. 10.2.14 [mysql Ver 15.1 Distrib 10.2.14-MariaDB, for Win64 (AMD64)].

I am presuming that there has been some change in the treatment of anomalous data inserts since the book was published. I am making a note of the different outcome for the benefit of the editors, author and other readers. I will try to troubleshoot this more later, but do not intend to take further time from the chapter now.

Suffice it to say that the paragraphs explaining how the anomalous data was going to populate the row didn't seem to apply to me.

* * * * *

Thanks!

THERE ARE NO PAGE NUMBERS GIVEN IN SAFARI BOOKS PRESENTATION OF THE BOOK.

At Chapter 7 -- Selecting Data
Within Paragraph 2 of the 1st page.

The last sentence of the 2nd paragraph (beginning "The simplest was to retrieve data from ...") reads:

"It's not necessary to know or use all of the may options, but some techniques such as joining tables together are basic to using relational databases."

The word "may" within this sentence probably should have read "many," yielding:

"It's not necessary to know or use all of the many options, but some techniques such as joining tables together are basic to using relational databases."

6 lines down 'hep Data Manipulation" should be "help data Manipulation"

The paragraph "Looking over the results..." the word "six" should be "five", as the original birds table only contained 5 columns.

Column name used at the end of the sentence continuation from the previous page should be `conservation_state` instead of `conservation_category`.

The 'AUTO_INCREMENT` variable should be equal to 7, since there are 6 birds in the table already. See page 74.

Code is missing a second open parenthesis on the first line. The SQL query should read:

`SELECT IF((CHAR......'

instead of:

`SELECT IF(CHAR......'

The questions asks the reader to use the `DATESUB()` function. The correct function name is `DATE_SUB()`.

The third part of the question asks the reader to use the `ADD_DATE()` function. The correct function is actually `ADDDATE()`.