MySQL Pocket Reference, Second Edition
by George Reese

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated February 27, 2008.


UNCONFIRMED  errors and comments from readers: 

{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?


(32) last two lines;
Do not break the literal -45198.2164e+10 into two pieces with a linebreak.


{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.


(35) lines 18-19;
"two dashes and a whitespace (--)" -> "two dashes (--) and a whitespace"


[89] line 13;
The operator <=> is mentioned, but this operator does not seem to be defined anywhere in the book.


[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.


(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".


(125) beginning of index;
The index does not begin with a symbols section listing + - * etc.


(126) N section of index;
The term NULL does not appear in the index. It is a fairly important component of SQL