Errata

Understanding MySQL Internals

Errata for Understanding MySQL Internals

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. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page 30
Item 8, second paragraph

$ ../client/mysql -uroot -host=127.0.0.1 -port=9306 test

should instead be:

$ ../client/mysql -uroot --host=127.0.0.1 --port=9306 test

If you use the - instead of -- it'll interpret the -h in -host to mean host and you'll end up with this:

ERROR 2005 (HY000): Unknown MySQL server host 'ost=127.0.0.1' (1)


Note from the Author or Editor:
Yes, this is correct. All options that have more than one letter in them require two dashes, not quite.

 Anonymous  Apr 11, 2010 
Chapter 10
Storage Engines - Table

Locking is wrongly spelled as - Lacking

Note from the Author or Editor:
Yes, it should say "Locking".

 Anonymous  Nov 10, 2008 
Printed
Page index
The entry for "binary log" should not point to p. 113. It should point to the following pages

214
216
220
223-227

 Anonymous   
Printed
Page 20
Item #1 in numbered list, and following

The free version of bitkeeper has changed since this was written.

The download is now www.bitmover.com/bk-client2.0.shar

Instead of the "sfioball" and "update" programs, the free version of bitkeeper now installs a single command, "bkf" that supports just a few of the standard bitkeeper subcommands:
bkf clone
bkf parent
bkf pull
bkf changes

Note from the Author or Editor:
Bitkeeper is no longer used for MySQL version control. The version control system has been switched to Bazaar. It appears that Oracle public repositories are out of sync with their actual development and public releases. Percona stepped in and is trying to keep the revision history in their repositories at

lp:percona-server/upstream-5.0
lp:percona-server/upstream-5.1
lp:percona-server/upstream-5.5
lp:percona-server/upstream-5.6

 Anonymous   
Printed
Page 212
first paragraph, line 4

"is such a way", should be "in such a way".

 Anonymous