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 |
---|---|---|---|---|
Printed | Page 3.4.4 Last line in section |
The phrase "The MySQL ET type..." should be "The MySQL SET type..." |
Anonymous | |
Printed | Page 3.8.2 End of section |
The description of the <=> operator is wrong; it does not match |
Anonymous | |
Printed | Page 16 Last paragraph |
On pages 16, and again on page 19, the phrase "To do this, you can copy support- |
Anonymous | |
Printed | Page 33 3rd paragraph |
In the last sentence of the 3rd paragraph of page 33, it is written that "On an ASCII |
Anonymous | |
Printed | Page 34 2nd paragraph |
The "SET" type is misspelled as "ET". |
Anonymous | |
Printed | Page 38 |
On INSERT, is the value supposed to be: |
Anonymous | |
Printed | Page 42 Table 3-5 |
Terry Pratchett's last name is misspelled as "Pratchet". |
Anonymous | |
Printed | Page 48 las paragraph |
You say "It returns true if both sides are null or false if both sides are not null" |
Anonymous | |
Printed | Page 48 bottom 3 paragraphs |
You should keep consistent case on non-sql keywords to |
Anonymous | |
Printed | Page 49 Under Membership Tests |
There are inconsistencies in case for the SQL syntax on this page. Since identifiers |
Anonymous | |
Printed | Page 53 Second "user input" under "Relevance Values" subheading |
The "WHERE" keyword should be removed from the select list in the statement below: |
Anonymous | |
Printed | Page 59 Last paragraph |
Refers to Chapter 15 for DATE_FORMAT() function reference. Should be Chapter 17. |
Anonymous | Apr 06, 2009 |
Printed | Page 68 3rd paragraph |
The 3rd command for creating startup/shutdown script isn't correct. It should be: |
Anonymous | |
Printed | Page 69 Fourth Paragraph - Shell Script in middle of page |
This formatting error creates a serious technical mistake. |
Anonymous | |
Printed | Page 72 last paragraph |
The last sentence tells the user how to configure the time portion of the slow query log. |
Anonymous | |
Printed | Page 91 Near bottom |
The example on the page shows the creation of an index as follows: |
Anonymous | |
Printed | Page 103 7th Paragraph |
"Specify the a specific" should be "Specify a specific" - the "the" should be |
Anonymous | |
Printed | Page 111 top |
generally, a $ prompt is the user and the # prompt is root. |
Anonymous | |
Printed | Page 148 Example 9-1, line 6 |
Line 6 is missing a semicolon. It reads: |
Anonymous | |
Printed | Page 151 first command line example |
Is: |
Anonymous | |
Printed | Page 214 3rd paragraph |
The reader is instructed to use escapeshellcmd() to escape dangerous charachters in |
Anonymous | |
Printed | Page 223 Example 11-5 index.php script (continued) |
There is an inconsistency in the code used with the PHP library function crypt(). |
Anonymous | |
Printed | Page 233 8th or 2nd to Last paragraph |
The writer incorrectly makes a distinction between using the |
Anonymous | |
Printed | Page 240 the 11th row before EOP in example 11-5 index.php script |
passwd= "".crypt($passwd, substr($user, 0, 2)) |
Anonymous | |
Printed | Page 260 The last sentence of the paragraph describing "length" argument |
Since the length of the string "make" is 4 (excluding the trailing null character), |
Anonymous | |
Printed | Page 267 2nd and 3rd comments in the code example |
*/ (closing symbol for comments) are missing. |
Anonymous | |
Printed | Page 288 Examples |
CREATE TABLE emp_review shows two Table_Options "AUTO_INCREMENT = 1, TYPE=InnoDB;" |
Anonymous | |
Printed | Page 296 'Examples' section |
The section |
Anonymous | |
Printed | Page 302 next to last paragraph |
The paragraph starts with "The list of tables to join..." and then goes on to specify |
Anonymous | |
Printed | Page 330 next to last paragraph |
For the FROM_UNIXTIME function, the description begins "Returns the date (in GMT) corresponding ..." - should be "(in the system timezone)". Also, the example conversion appears to be incorrect. On my (MySQL 4.0.17) system, I get "select from_unixtime(903981584 + 3600 * 4 + 18)" => "1998-08-24 18:00:02" |
Anonymous | Apr 06, 2009 |
Printed | Page 381 mysql_num_rows description |
int mysql_num_rows(MYSQL_RES * result) |
Anonymous |