Errata

The 1st SQL command there is a single quote missing on line 4 after the word premium. The error in the PDF version is different from the error in the printed version. Printed version mysql> SELECT message_text, user_name -> FROM message -> INNER JOIN user ON message.user_id=user.id -> WHERE user.account_type='premium /* ERROR: single quote missing after the word premium */ -> ORDER BY message.published DESC LIMIT 10; PDF version: mysql> SELECT message_text, user_name -> FROM message -> INNER JOIN user ON message.user_id=user.id -> WHERE user.account_type='premiumv /* ERROR: the letter v in the word premiumv should be replaced with a single quote */ -> ORDER BY message.published DESC LIMIT 10;

Note from the Author or Editor:
This is likely a problem with a character. Perhaps a special character like a curly quote was in the final manuscript.

The lowermost leaf page in the diagram has a break between the two "Basinger, Viven" entries, indicating there are many entries between them, but the top paragraph of page 151 refers to those entries as the "last two entries" and at least implies that they are adjacent entries. The graphic should be amended such that the break is between "Barrymore, Julia" and the leftmost "Basinger, Vivien", so as to be less potentially confusing.

The book recommends 'log_slow_queries'. Result: "[Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead." Changing it to 'slow_query_log' as suggested eliminates the warning for me.

Note from the Author or Editor:
Please add a footnote after "good starting point" in the first para. The footnote should read: Please note that newer versions of MySQL remove, deprecate, and change some options; check the docs for details.

Trailing comma before semi-colon to end statement. ...IDENTIFIED BY 'p4ssword',; should be ...IDENTIFIED BY 'p4ssword';

There is a statement that MySQL efficiency will level off beyond 128MB (megabyte) of RAM. Is this correct or should it be GB?

Note from the Author or Editor:
In "Scaling by Consolidation", change to level off. A similar thing happens beyond 128 MB of memory, and MySQL can’t even to to level off. A similar thing happens beyond 128 GB of memory, and MySQL can’t even

URL for the page is: http://proquest.safaribooksonline.com/book/databases/mysql/9781449332471/6dot-query-performance-optimization/id3662101?uicode=califa Chapter 06 Section: Limitations of the MySQL Query Optimizer Sub-section: Correlated Subqueries 1st sentence of 2nd paragraph of the sub-section says: It�s tempting to think that MySQL will execute this query from the inside out, by finding a list of actor_id values and substituting them into the IN() list. It should say: It�s tempting to think that MySQL will execute this query from the inside out, by finding a list of [film_id] values and substituting them into the IN() list.

Note from the Author or Editor:
The exact wording of the text should be It’s tempting to think that MySQL will execute this query from the inside out, by finding a list of film_id values and substituting them into the IN() list.