Errata

MySQL Pocket Reference

Errata for MySQL Pocket Reference

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.

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 17
In the table, the function for "(real),(double)"

ePub version (reading on a Sony Reader)

Text shows as "Cash to a floating point number" and should read "Cast to a floating point number".

This is also true for the printed version (I own both) which I'll log now.

 Jonathan Haddock  Sep 23, 2009 
Other Digital Version 17
Please ignore my previous errata for this book

Please ignore my previous errata for this book (17
In the table, the function for "(real),(double)")

I meant to place this on the PHP book, not MySQL...

 Jonathan Haddock  Sep 23, 2009 
Printed Page 32
section on binary literals

Key information is missing here: How are the hex values 00-1f and 7f-ff represented in a binary literal?

 Anonymous   
Printed Page 32
last two lines

Do not break the literal -45198.2164e+10 into two pieces with a linebreak.

 Anonymous   
Printed Page 34
second paragraph

This paragraph is rather confusing. The first sentence says that any character may be used in an
identifier. This is immediately contradicted by the third sentence which begins "This rule is limited".
Finally, the last sentence in the paragraph states "MySQL 5 lifts these restrictions." Just which
restrictions are lifted is quite unclear at this point. -- Suggestion: Clearly describe the syntax of
each different type of identifier and make clear which entities must adhere to which syntax.

 Anonymous   
Printed Page 35
lines 18-19

"two dashes and a whitespace (--)" -> "two dashes (--) and a whitespace"

 Anonymous   
Printed Page 89
line 13

The operator <=> is mentioned, but this operator does not seem to be defined anywhere in the book.

 Anonymous   
Printed Page 89
section on comparison operators

Each operator description begins with "Match rows". The operators in fact do not match rows; they simply
compare their operands. It may be that in some instances ultimately a database row is selected based on a
logical expression (which might contain many comparison operators), but this is just a particular use of
the comparison operators. They do not match rows; they compare operands.

 Anonymous   
Printed Page 91
sections on OR and AND

Since these operators always take exactly two arguments, the phrase "if any of the arguments" should
perhaps be "if either of the arguments".

 Anonymous   
Printed Page 125
beginning of index

The index does not begin with a symbols section listing + - * etc.

 Anonymous   
Printed Page 126
N section of index

The term NULL does not appear in the index. It is a fairly important component of SQL

 Anonymous