Errata

SQL Pocket Guide

Errata for SQL Pocket Guide, Fourth Edition

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page V4 - Preface XVI
"How to Contact Us" area just below the address for O'Reilly

Ms Zhao, first let me say that I am enjoying your 4th edition of SQL Pocket Guide.

I believe this is just a typo from the publisher. On Preface page XVI, I wanted to see the additional web page mentioned. I found the following link not working. https://oreil.ly/jreAj.

Fortunately, I quick telephone call to O'Reily and speaking with Jennifer, a very
nice and efficient Customer Service person, my problem was solved. She emailed me the correct link and I have now incorporated the information into my book. The working link is https://www.oreilly.com/catalog/errata.csp?isbn=0636920415275

Sincerely,

Stan Moore

Stanley Moore  Oct 20, 2021  Dec 06, 2021
Printed
Page Cover
Top right corner

From a marketing perspective, one of the things that people like about the book and prompt them to buy the book is that it covers multiple flavors of SQL. This isn't prominently displayed on the cover, however.

Could the text at the top right corner of the cover slightly be updated, so that it matches the format of the 3rd edition of the book?

Current state:
4th Edition

Suggested state:
4th Edition
MySQL, Oracle, PostgreSQL, SQL Server, SQLite

Alice Zhao
Alice Zhao
 
Oct 26, 2021  Dec 17, 2021
Printed
Page 1
Under the SQL section, under the first paragraph

Currently the text is:

English: "Hey app. When is my husband's birthday?"
SQL: SELECT * FROM birthdays
WHERE person = 'husband';

The problem is that the SQL code should all be on one line OR the SELECT / FROM / WHERE terms should be at the start of each line. I recommend the following (to match the formatting at the top of page 4):

English
"Hey app. When is my husband's birthday?"
SQL
SELECT * FROM birthdays WHERE person = 'husband';

English and SQL should be italicized, and the SELECT statement should be in the code font.

Alice Zhao
Alice Zhao
 
Sep 09, 2021  Dec 17, 2021
Printed
Page 40
Top

The notes at the top of pages 40 and 41 have different capitalization. They should match.

Should I follow the standards?
Which Standard Should I Choose?

Alice Zhao
Alice Zhao
 
Sep 09, 2021  Dec 17, 2021
Printed
Page 74
Last paragraph of the tip

The formatting of the Show... section should match the formatting of the Filter... section. Specifically, the (or... Server) section should be moved down a line and indented like the Better yet... section above.

Filter by a column within the WHERE clause
Better yet, filter by a column that is already indexed to make the retrieval even faster.

Show the top few rows of data with the LIMIT clause
(or WHERE ROWNUM <= 10 in Oracle or SELECT TOP 10 * in SQL Server)

Alice Zhao
Alice Zhao
 
Sep 09, 2021  Dec 17, 2021
Printed
Page 109, 237, 269, 272, 311
Headers in the tables

During production, I requested that the indentation be removed from any column with bolded code. I see that this was applied in some of the tables in the book, but there are a few that were missed:

Table 5-8 on page 109
Table 8-1 on page 237
Table 9-1 on page 269
Table 9-2 on page 272 (there is no bolding, but the indentation issue is still there)
Table 10-1 on page 311

Alice Zhao
Alice Zhao
 
Sep 09, 2021  Dec 17, 2021
Page 180
Table 7-1

The last line in column 2 currently shows:

v=

Instead, it should be:

>=

Note from the Author or Editor:
Confirmed

Alice Zhao  Feb 07, 2022 
Printed
Page 273
Entire table

The third column of the table is squished and the code inside wraps around. This is likely due to me requesting that NATURAL stay one word within the first column. It is more important for the code in the third column not to wrap around, so please remove the NATURAL constraint and widen the third column.

Alice Zhao
Alice Zhao
 
Sep 09, 2021  Dec 17, 2021
Printed
Page 274
Top right cell

The > before the SELECT statement should be removed. It should look like:

SELECT *

instead of:

>SELECT *

Alice Zhao
Alice Zhao
 
Sep 09, 2021  Dec 17, 2021