Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date submitted |
---|---|---|---|---|
Other Digital Version | N/A Chapter 5: location 2723 in the Kindle version |
The query and the results do not match (the book shows results ordered by city). |
Wim Olivier | Aug 28, 2021 |
Other Digital Version | N/A Chapter 5, Using the same table twice |
In the Kindle version: |
Wim Olivier | Aug 29, 2021 |
Other Digital Version | Chapter 4 Exercise 4-3 |
The table name reference for the query is wrong. The correct table name is 'payment' not 'payments' |
Oluwatosin Ogunfile | Jan 18, 2022 |
Printed, PDF, ePub, Mobi, , Other Digital Version | Page Preface Preface |
The preface for this title references katakoda.com, which is no longer available to the public. The URL is no longer functional. |
Anonymous | Oct 05, 2022 |
Page Page 69 "Using the not Operator" section |
I believe there is a typo in the description of the negation of the OR statement used in the example: |
Anonymous | Oct 27, 2022 | |
Printed | Page 33 Below the tip |
The keyword is 'describe', and the example is 'desc'. |
Josh Fry | Feb 10, 2022 |
Printed | Page 41 first code |
HI, |
Yossi Reichman | Aug 30, 2023 |
Printed | Page 49 Query and table at bottom of page |
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. |
Anonymous | Feb 27, 2022 |
Printed | Page 62-63 top of page 63 |
The output table is wrong. The code is supposed to order first by last name, next by first name -- however in the output table, no ordering with respect ot first name is done. For example, focus on last_name that starts with M and see how first name is not ordered. |
Anonymous | Jan 16, 2022 |
Page 119 Including special characters. CHAPTER 7th |
Type SELECT CHAR(97,98,99,100,101,102,103); retrieves in hexadecimal form: |
Anonymous | Jan 25, 2023 | |
Printed | Page 183 example at bottom of the page |
Assuming the subquery at the bottom of page 183 returns 3, why is the result not sorted on the actor's last name, seeing that that is the third SELECTed field? |
Anonymous | Jul 20, 2021 |
Printed | Page 209 first code block |
Example database has no customer with zero rentals. So you cannot really test this code. When I created a customer with no rentals, the proposed null-handler still returned null since the numerator was null. |
Gregory Truby | Apr 24, 2024 |
Printed | Page 210 Section "Handling Null Values" |
I understand that this is an attempt to show the reader how to handle null values and I'm sure the code would work. However, when I tried to create a record where this safety net would kick in, I couldn't. There is a constraint in the database that prevents one from adding a record to the customer table with no address_id. |
Gregory Truby | Apr 24, 2024 |
Page 236 at the bottom |
There is a typo in the second bullet point of foreign key constraints. |
Qichun Dai | Sep 01, 2021 | |
Printed | Page 257 1st |
oreil.ly/qV7sE |
Sophia | Nov 06, 2022 |