Errata
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
| Version |
Location |
Description |
Submitted By |
| Safari Books Online |
chapter 1.4.
chapter 1.4., first enumeration, first item |
"InnoDB must find a version of the row that is at least as old as the transaction"
should be
"InnoDB must find the youngest version of the row that is at least as old as the transaction"
note on the errata submission form: Safari Books readers cannot determine page numbers
|
Anonymous |
| Printed |
Page 48
first code snippet |
"The following command runs the random read/write access file I/O benchmark:
$ sysbench --test=fileio --file-total-size=150G --file-test-mode=rndwr --init-rnd=on --max-time=300 --max-requests=0 run"
The --init-rnd option is not recognized by sysbench v0.4.8 on FC7, compiled from source.
It should be "--init-rng=on" instead.
|
Anonymous |
| Printed |
Page 69
last paragraph (6) |
"represented as base-64 by default"
should be:
"represented as base-16 by default"
|
Anonymous |
| Printed |
Page 116
Figure 3-8 |
This is request for clarification:
You mention that indexes, including secondary ones, are always sorted based on the key. In this example, you have 10K entries and col2 ranges between 0-100, randomly chosen. The secondary index (here for InnoDB) on col2 will have many similar values (avg: 10K/100). So, for the leaf nodes, when the secondary index is similar, will the 'pointers' ie primary key values be used for sorting? However, in your fig 3-8, this is how you show -- see 8->18 followed by 8->99. Would also like to know that if primary key is participating in sort, is that by design or based on implementation -- if latter, then I will be skeptical since there's no gurantee of similar implementation in future releases.
Please clarify these. Thanks for the good book, BTW.
|
Anonymous |
| Printed |
Page 140
Last paragraph |
The description of the subsequent query is incorrect. It says "... view the last 10 messages from each of the premium users." Since there's no "group by" in the query, it will actually return the last 10 messages by any premium user. In other words, if there are 5 premium users, the query returns up to 10 records, not up to 50 records.
|
Anonymous |
| Printed |
Page 179
4th paragraph |
Replace "....by finding a list of actor_id values and substituting them..."
with:
"....by finding a list of film_id values and substituting them..."
|
Anonymous |
| Printed |
Page 211
Host matching, 3rd list |
I think this list was sorted by wrong order.
this book says:
@joe.example.com
@%.example.com
jane@%.example.com
jane@%
I think:
@joe.example.com
jane@%.example.com
@%.example.com
jane@%
|
Anonymous |
| Printed |
Page 354
5th paragraph |
Written as:
innodb_flush_logs_at_trx_commit=1
should be (without the s in logs):
innodb_flush_log_at_trx_commit=1
|
Greg Lindholm |
"This is a good book that is well worth the cost. While it is not a newbie book, there is plenty here for novice and expert alike. I can pretty much guarantee that if you work with, or want to work with, MySQL, you will get some value from it."
--Lewis Cunningham, MySQL Database News
