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 xi Preface, "Purpose" Change |
"...Open Source software even through their licenses..." |
Anonymous | |
Printed | Page xiii |
The book reads: |
Anonymous | |
Printed | Page ... servlet." |
However, no such code was included in the paragraph, or in any examples |
Anonymous | |
Printed | Page 4 second sentence on bottom paragraph |
"The file system file is the electronic..." |
Anonymous | |
Printed | Page 5 Table 1-2: Kurt Rambis is no longer coaching the Lakers. |
Anonymous | ||
Printed | Page 9 paragraph before "The History of MySQL", last sentence: remove the |
second "to". |
Anonymous | |
Printed | Page 9 last word of footnote: "memeory" is misspelled. |
Anonymous | ||
Printed | Page 10 "The History of MySQL" Change |
"...Win32, and OS/2. TCX estimates that..." |
Anonymous | |
Printed | Page 10 6th complete paragraph, last word should be "servers", not |
"severs". |
Anonymous | |
Printed | Page 16 Figure 2-2: the order of attributes is different from Table 2-1. |
Anonymous | ||
Printed | Page 16 Figure 2-2: "Record Name" should be "Record Label". |
Anonymous | ||
Printed | Page 17 Figure 2-3: for the CD entity, the attributes are ordered |
differently than in fig. 2-2 and table 2-1. |
Anonymous | |
Printed | Page 20 Figure 2-6: CD entity is missing "Band Name" and Song entity |
should have a "Song ID" and "Song Name" instead of a "Song Name ID". |
Anonymous | |
Printed | Page 22 1st sentence: "If one of the sides as a degree..." should be |
"If one of the sides has a degree..." |
Anonymous | |
Printed | Page 22 2nd paragraph, 1st sentence: "The final kind of relationships..." |
should be "The final kind of relationship..." |
Anonymous | |
Printed | Page 22 2nd paragraph, 2nd sentence: singular rather than plural form |
should be used. |
Anonymous | |
Printed | Page 25 Figure 2-12: The State entity should have "State ID" rather than |
"State Code"; it also needs the attribute "State Abbreviation". |
Anonymous | |
Printed | Page 25 Figure 2-12: The Record Label entity should not have "State Name" |
and "State Abbreviation" attributes. |
Anonymous | |
Printed | Page 26 In paragraph 2 you mention that: |
"We covered an approach to creating such a model which is in-line |
Anonymous | |
Printed | Page 27 Table 2-2: SongLength is missing from the Song table. |
Anonymous | ||
Printed | Page 27 Table 2-2: RecordLabelName and RecordLabelId cannot both be |
primary keys. |
Anonymous | |
Printed | Page 27 Table 2-2: In the "Notes" column for the last row, the phrase |
"primary key" should be deleted from the table. |
Anonymous | |
Printed | Page 28 Table 2-3: SongLength is missing from the Song table. |
Anonymous | ||
Printed | Page 29 Example 2-1, 2nd line: should have "RECORD_LABEL_ID" instead of |
"RECORD_LABEL_I". Also, the Song table is missing "SONG_LENGTH", the Song |
Anonymous | |
Printed | Page 29 Example 2-1: The spacing should be adjusted so all tables read as |
clearly as the Song table. |
Anonymous | |
Printed | Page 29 Example 2-1: There are various indentation, spelling, and logical |
errors too numerous to identify here. The example should be replaced with |
Anonymous | |
Printed | Page 29 Example 2-2: In the Artist table, the ARTIST_ID should be "INT NOT |
NULL" rather than "INT NO NULL". SONG_LENGTH and a foreign key for Artist |
Anonymous | |
Printed | Page 29 Example 2-2: There are various indentation, spelling, and logical |
errors too numerous to identify here. The example should be replaced with |
Anonymous | |
Printed | Page 30 Last sentence |
Sentence suggests installing from source, which conflicts with p41, |
Anonymous | |
Printed | Page 33 Table 3-1: The two primary sites for MySQL would be more prominent |
and obvious if they were in boldface. |
Anonymous | |
Printed | Page 34 2nd full paragraph after file list, 4th sentence: "This is a case |
for the last..." should be "This is the case for the last..." |
Anonymous | |
Printed | Page 34 The first step to 'Installing from Source' is to |
|
Anonymous | |
Printed | Page 35 1st paragraph, last sentence: "Running with the--help..." should |
have a space between "the" and "--help". |
Anonymous | |
Printed | Page 35 The "with-low-memory" option should have two dashes before it, |
rather than an em dash. |
Anonymous | |
Printed | Page 35 under the "localstatedir" option: "/usr/local/var" should probably |
have a trailing slash. |
Anonymous | |
Printed | Page 35 (penultimate paragraph) - "installing MySQL from source" says that the |
mysql_install_db script " ..will also start the server daemon" |
Anonymous | |
Printed | Page 36 in the list of installation steps: the first step should be |
"gunzip..." rather than "gzip..." |
Anonymous | |
Printed | Page 36 just a note about binary distributions: there are also rpm and deb |
distributions available. |
Anonymous | |
Printed | Page 36 'To summarize, a sequence of installaion steps look like this:' |
The first step is to gzip !!! |
Anonymous | |
Printed | Page 37 1st paragraph of mSQL section, 2nd sentence: the URL should end |
with "au" rather than "avl". |
Anonymous | |
Printed | Page 38 in the sequence of installation steps, the first step should be |
"gunzip..." |
Anonymous | |
Printed | Page 40 Figure 4-1: The caption should have "server" rather than "sever". |
Anonymous | ||
Printed | Page 41 2nd paragraph after "Running MySQL", 2nd sentence: is the path |
correct or does it need a "mysql" in the middle? If not, then the path on |
Anonymous | |
Printed | Page 49 a.) Change "-# LOG" to "-# debug" ... ? |
b.) Some relevant information about the MySQL version I'm using: |
Anonymous | |
Printed | Page 50 2nd paragraph after "Backups", last sentence: "...next most |
important form up backup...", the "up" should be "of". |
Anonymous | |
Printed | Page 50 3rd paragraph after "Backups", 3rd sentence: "...or some similar |
data." should be "...or some similar schedule." |
Anonymous | |
Printed | Page 50 second paragraph.... |
"In this section, we will focus on the next most important form up |
Anonymous | |
Printed | Page 50 Backups, 3rd para, 3rd sentence |
Statement 'back up all data once a week or some similar data' |
Anonymous | |
Printed | Page 51 1st paragraph after "Security", 3rd sentence: perhaps "mysql" (the |
database) could be in constant width font? Also, the period should be |
Anonymous | |
Printed | Page 51 underneath "The user table", the last sentence is redundant and |
would be better as "The user table has the structure shown in Table 4-1:" |
Anonymous | |
Printed | Page 51 Chapter 4, "Backups" Change |
"...do it often and that your periodically check your..." |
Anonymous | |
Printed | Page 51 Table 4-1: "Insert_riv" should be "Insert_priv". |
Anonymous | ||
Printed | Page 53 the list of SQL INSERT statements would be easier to read if the |
"VALUES" lines were indented about 7 characters. |
Anonymous | |
Printed | Page 54 Table 4-2: "Insert_riv" should be "Insert_priv". |
Anonymous | ||
Printed | Page 55 Table 4-3: "Insert_riv" should be "Insert_priv". |
Anonymous | ||
Printed | Page 56 Penultimate sentence |
The word 'user' should be in constant width as it is a keyword |
Anonymous | |
Printed | Page 57 This problem lies in the last sentence before demonstration of |
the mysqlaccess utility. |
Anonymous | |
Printed | Page 58 paragraph after "MySQL Utilities", last sentence: the reference to |
"Chapter 18, PHP and Lite Reference" should refer to "Chapter 17, MySQL and |
Anonymous | |
Printed | Page 59 paragraph after "Third Party Tools", 2nd sentence: should refer to |
"Inprise's Delphi" rather than "Inrpise's Delphi". |
Anonymous | |
Printed | Page 61 1st sentence after "Sqlscreens": the first "databases" should be |
singular. |
Anonymous | |
Printed | Page 63 very top sentence: "...just how MySQL works under the covers..." |
is a morally questionable statement! :) A more common expression is "...just |
Anonymous | |
Printed | Page 63 table_cache 'mysqld' option |
The book reads: |
Anonymous | |
Printed | Page 65 2nd sentence next to the turkey: there should be a space between |
"isamchk" and "-r". |
Anonymous | |
Printed | Page 70 Figure 5-1: 5 clients each with an arrow is shown pointing to 4 |
queries. What does this mean? |
Anonymous | |
Printed | Page 70 1st complete paragraph, last sentence: "...enables any C program |
to connect to a mSQL server...", the "a" should be "an". |
Anonymous | |
Printed | Page 73 is the unix command for starting the daemon "9781565924345d2 &" or "msql2d &"? |
Anonymous | ||
Printed | Page 74 1st complete paragraph, 1st sentence: "While the Win32 does not |
yet..." should be "While the Win32 version does not yet..." |
Anonymous | |
Printed | Page 75 2nd paragraph, 3rd sentence: "...they are followed by the |
character when using..." Followed by what character? |
Anonymous | |
Printed | Page 75 second text paragraph contains |
followed by the character when |
Anonymous | |
Printed | Page 77 under "Unix_Port" option, 2nd sentence: "%I%" does not need the |
second "%". |
Anonymous | |
Printed | Page 83 in the format shown for the 9781565924345.acl file, the 2nd stanza: |
"wriite" should be "write". |
Anonymous | |
Printed | Page 84 last sentence on page: "...and a -f options enables you..." the |
"options" should be singular. |
Anonymous | |
Printed | Page 85 under "9781565924345export", 2nd sentence: the word "database" should be |
plural, or more properly "database management systems". |
Anonymous | |
Printed | Page 88 under "mSQL-JDBC", last sentence: there should be a comma after |
"discusses". |
Anonymous | |
Printed | Page 90 after "SQL Basics", 3rd sentence: refers to "...a SQL grammar..." |
but the rest of the book refers to SQL as "an SQL". |
Anonymous | |
Printed | Page 92 near bottom of page, sentence before 2nd CREATE TABLE example: |
"The CREATE example above could just as well appeared:", the last word |
Anonymous | |
Printed | Page 93 after example table, 2nd sentence: "A field's datatype |
specified..." should be "A field's datatype specifies..." |
Anonymous | |
Printed | Page 93 Chapter 6, "The Design of SQL" Change |
"This first element of an SQL query..." |
Anonymous | |
Printed | Page 93 Chapter 6, "Creating and Dropping Tables" Change |
"A field's datatype specified what kind of data the field can hold." |
Anonymous | |
Printed | Page 93 1st paragraph |
Should the text: |
Anonymous | |
Printed | Page 94 after "SQL Datatypes", 2nd sentence: to be consistent, the |
reference to "...a SQL datatype..." should be "...an SQL datatype..." |
Anonymous | |
Printed | Page 94 DROP TABLE table_name IF EXISTS |
should be: |
Anonymous | |
Printed | Page 96 paragraph after "Character Types", 5th sentence: "The important |
fact to note here is that indexing one character..." the "one" should be |
Anonymous | |
Printed | Page 98 Last word |
'That is a 41% savings!' should read |
Anonymous | |
Printed | Page 98 last paragraph, 3rd sentence: 576 bytes is 144x4 not 144x3. |
Anonymous | ||
Printed | Page 98 Chapter 6, "Variable-length character fields in mSQL" Change |
"If you multiple that times thousands..." |
Anonymous | |
Printed | Page 99 Chapter 6, "Enumerations and Sets" Change |
"The ENUM type allows you specify at table creation..." |
Anonymous | |
Printed | Page 99 paragraph after "Binary Datatypes", last sentence: shouldn't |
binary data be sorted in case-sensitive, not insensitive order? |
Anonymous | |
Printed | Page 99 Binary Datatypes, second sentence |
Should be a comma between CHAR and BINARY. |
Anonymous | |
Printed | Page 99 1st paragraph after "Enumerations and Sets", 2nd sentence: "The |
ENUM type allows you specify..." there should be a "to" between "you" and |
Anonymous | |
Printed | Page 99 "Enumerations and Sets," 1st paragraph |
In the following passage: |
Anonymous | |
Printed | Page 100 There are two problems in the first full paragraph |
1) It refers you to Chapter 17 for the data type descriptions, that should |
Anonymous | |
Printed | Page 100 last sentence before "Indices" section: the reference should be |
to "Chapter 15, SQL Reference" instead of "Chapter 17, MySQL..." |
Anonymous | |
Printed | Page 100 before "Indices" section: I have not noticed any support for the |
MONEY type in MySQL. |
Anonymous | |
Printed | Page 102 3rd paragraph after "mSQL sequences", 1st sentence: "...and will |
increase by 5 each time some accesses the sequence." The "some" should be |
Anonymous | |
Printed | Page 102 In the 9781565924345 sequence, you have |
CREATE SEQUENCE ON table_name [VALUE start STEP incr] |
Anonymous | |
Printed | Page 102 The first paragraph readsL |
"The AUTO_INCREMENT row must be indexed." |
Anonymous | |
Printed | Page 102 |
The first example reads: |
Anonymous | |
Printed | Page 106 1st paragraph after "Joins", 2nd sentence: "...enable you to |
match a row from one table up with a row..." would read more clearly |
Anonymous | |
Printed | Page 109 1st paragraph after "Extended Functionality", 1st sentence: |
"...in the other database engine." the "engine" should be plural. |
Anonymous | |
Printed | Page 109 paragraph after "MySQL Features", 4th sentence: "For example, the |
function SQRT(16) returns 4." The "4" should be in constant width font. |
Anonymous | |
Printed | Page 110 Last example before pahagraph at bottom of page |
The salt is two random characters stored at the beginning of the encrypted password |
Anonymous | |
Printed | Page 111 at the top of the page: the SELECT example should include the |
book table in the FROM clause. |
Anonymous | |
Printed | Page 111 I think natural outer join is a bit under-explained. Sample |
initial tables and returned rows would be usefull |
Anonymous | |
Printed | Page 113 3rd paragraph, last sentence: "import" should be "important". |
Anonymous | ||
Printed | Page 114 3rd paragraph: "Open Source" is not and has never been a |
trademark. |
Anonymous | |
Printed | Page 117 2nd paragraph after "Objects", 1st sentence: "System" should be |
added after "Management". Also, "...simply a list of records..." should be |
Anonymous | |
Printed | Page 118 4th complete paragraph, 5th sentence: "...increase for demand..." |
should be "...increased demand..." |
Anonymous | |
Printed | Page 118 1st paragraph under "GNU SQL", last sentence: "...one glaring |
omissions..." the "omissions" should be singular. |
Anonymous | |
Printed | Page 118 In the fourth paragraph |
"ranks up their in popularity with" |
Anonymous | |
Printed | Page 122 I am not sure it but is in chapter 10 on the web.... |
Error: |
Anonymous | |
Printed | Page 124 Figure 8-1: How does this figure explain the client/server |
architecture? Does the one-way arrow mean that the client sends something to |
Anonymous | |
Printed | Page 125 1st paragraph, last sentence: "...a badly written system..." |
perhaps the "system" should be "application" or "client"? |
Anonymous | |
Printed | Page 126 the "Rules of Thumb" box and the note next to the turkey icon |
both interrupt the flow of reading. Perhaps they could be placed at the end |
Anonymous | |
Printed | Page 126 1st paragraph, 2nd sentence: "each row from the database..." the |
"each" should be capitalized. |
Anonymous | |
Printed | Page 127 Figure 8-3: The "Address" object is missing a field for "state". |
Also, what does the "1" indicate at the end of the arrow? |
Anonymous | |
Printed | Page 127 paragraph before "The Three-tier Architecture": this paragraph |
twice refers to a "Company" class. This should be "Address" instead. |
Anonymous | |
Printed | Page 128 paragraph next to the owl icon, 2nd sentence: the period should |
be removed from "ultra-thin client.". |
Anonymous | |
Printed | Page 128 paragraph next to the owl icon, last sentence: "...the most |
client processing..." the "most" should probably be "majority of" or |
Anonymous | |
Printed | Page 132 Describes earlier habit of capitalizing starting HTML tags |
and lowercasing ending tags as a convention. I've worked and conversed |
Anonymous | |
Printed | Page 134 example 9-1: the closing "</head>" is missing. |
Anonymous | ||
Printed | Page 135 first paragraph after "Example 9-1" |
The author mentions the IMAGE style as usually being incompatible with "hearing- |
Anonymous | |
Printed | Page 136 Bullet points |
'Standard output' is described below bullets as being a method of |
Anonymous | |
Printed | Page 137 1st paragraph after "Environment Variables", 2nd sentence: |
"...unofficial ones that are used..." the "that" should be removed. |
Anonymous | |
Printed | Page 137 1st paragraph after "Environment Variables", last sentence should |
be "Table 9-1 lists the CGI..." |
Anonymous | |
Printed | Page 137 Table 9-1 lists 15 variables, but the paragraph before said there |
are 17 standard variables. |
Anonymous | |
Printed | Page 137 Sentence before Figure 9-1 |
The form data given appears to be from a non-existant example. |
Anonymous | |
Printed | Page 139 1st para, last sentence |
'finger root' is a UNIX/Linux command and thus should be in a different |
Anonymous | |
Printed | Page 139 Chapter 9, "Standard Input" Change |
"...can be found on Yahoo at..." |
Anonymous | |
Printed | Page 140 |
in Example 9-2, the comment for the line "@fields..." should read : |
Anonymous | |
Printed | Page 140 in Example 9-2, the 4th line from the bottom of the page should |
have a "#" in front of it. |
Anonymous | |
Printed | Page 140 second footnote... "mit" should be italicized like rest of |
URL |
Anonymous | |
Printed | Page 141 in Example 9-2, the 2nd comment line after "foreach..." could use |
a closing parenthesis ")". |
Anonymous | |
Printed | Page 141 Example 9-3 |
If the given source code is pure C, both 'llist' and 'node' should |
Anonymous | |
Printed | Page 144 1st complete paragraph, the 3rd sentence seems to be talking |
about laundry. Perhaps it should read: "Needless to say, this hampers |
Anonymous | |
Printed | Page 144 Figure 9-2, the 2nd invocation of the CGI program should be |
labeled with "invoke" rather than "involve". |
Anonymous | |
Printed | Page 147 in Example 9-4, the 2nd line on the page should close the HTML |
with "</body></html>". |
Anonymous | |
Printed | Page 147 3rd paragraph, 4th sentence: "...the direction in wish you |
want..." the "wish" should be "which". |
Anonymous | |
Printed | Page 148 Chapter 9, Example 9-5 Change |
"} elsif ( not $output->param('start') ) {" |
Anonymous | |
Printed | Page 150 Chapter 9, "Security" Change |
"$|++; # Disable the buffering in the child as way." |
Anonymous | |
Printed | Page 150 the example CGI program could use better formatting of the |
comments. |
Anonymous | |
Printed | Page 150 perl code, line starting with "$pid"... wraps leaving part |
of a comment ("opens a") on the subsequent line, uncommented. |
Anonymous | |
Printed | Page 152 the paragraph next to the owl icon, 2nd sentence, parenthetical |
comment: "...as opposed to nonweb connected databases..." should be "...as |
Anonymous | |
Printed | Page 155 Sentence before Perl code |
'...you must use DBI to get access:' - use is a Perl keyword in this |
Anonymous | |
Printed | Page 157 |
The bottom of the code reads: |
Anonymous | |
Printed | Page 158 |
The fifth line in the code sample reads: |
Anonymous | |
Printed | Page 159 Example 10-3, there are a couple points that seem would fail |
under use strict: neither $table or $server are declared with 'my' |
Anonymous | |
Printed | Page 159-161 The code provided does not compile, and |
also is missing some critical variable definitions. |
Anonymous | |
Printed | Page 160 The listing for Example 10-3 appears to be incorrect. The lines |
my @fields = @{$table_data->NAME}; |
Anonymous | |
Printed | Page 174 |
The last paragraph in the July 1999 printing reads: |
Anonymous | |
Printed | Page 181 1st paragraph, 3rd sentence: "...an excellent introduction into |
Python..." the "into" should be "to". |
Anonymous | |
Printed | Page 181 1st paragraph, 3rd sentence: the 2nd author's last name is |
"Ascher" with a "c". |
Anonymous | |
Printed | Page 182 1st complete paragraph, 2nd sentence beginning "You should not |
use the from..." is very confusing. |
Anonymous | |
Printed | Page 182 First paragraph after 9781565924345 code block |
Note that this was found in the first printing (July 1999), but it has not |
Anonymous | |
Printed | Page 184 paragraph after "Updates", last sentence: "...the AUTO_INCREMENT |
value of the table..." the "of" should be "if". |
Anonymous | |
Printed | Page 194 $query = "select * from sharks where " |
But it should have been: |
Anonymous | |
Printed | Page 194 Chapter 12, "PHP" Change |
|
Anonymous | |
Printed | Page 194 Line 15 |
Through my tests "+=" only works with numbers in PHP. To make it work with |
Anonymous | |
Printed | Page 194 Chapter 12, "PHP" Change all occurences of |
'<!' |
Anonymous | |
Printed | Page 194 Throughout example code |
In the section on PHP, there are several errors. |
Anonymous | |
Printed | Page 197 1st paragraph, 1st sentence: a colon would be slightly more |
appropriate after "programming languages". |
Anonymous | |
Printed | Page 198 In the table of functions, the function |
|
Anonymous | |
Printed | Page 199 The call to mysql_real_connect contains too few arguments. |
Anonymous | ||
Printed | Page 199 Example 13-1, line 11 |
connection=mysql_real_connect(&mysql, |
Anonymous | |
Printed | Page 200 command line for compilation: (one third up from bottom of page) |
gcc -L/usr/local/mysql/lib -I/usr/local/mysql/include -o select |
Anonymous | |
Printed | Page 201 Example 13-2: the comment in the 17th line, "/* the return |
balue..." should be "/* the return value..." |
Anonymous | |
Printed | Page 202 3rd paragraph, 2nd-to-last sentence: "...issue of great |
importance in more..." there should be an "a" before "more". |
Anonymous | |
Printed | Page 203 footnote: "...documenting the object-oriented..." the "the" |
should probably be removed. |
Anonymous | |
Printed | Page 204 Figure 13-1: the objects shown here differ in small details from |
the objects as defined in the headers. Each object has a Close() method |
Anonymous | |
Printed | Page 206 1st paragraph, 3rd sentence: "...using a mSQL calls the..." the |
"a" should be removed. |
Anonymous | |
Printed | Page 206 The call to mysql_real_connect contains too few arguments. |
Anonymous | ||
Printed | Page 206 14 lines up from the bottom of Example 13-4 |
mysql_real_connect needs 8 parameters and not 7 |
Anonymous | |
Printed | Page 211 1st paragraph under "Result Sets", 1st sentence: "...an |
abstraction on the..." should be "...an abstraction of the..." |
Anonymous | |
Printed | Page 211 1st paragraph under "Result Sets", 2nd sentence: "Specifically, |
should..." should be "Specifically, it should..." |
Anonymous | |
Printed | Page 211-212 The class definition for result.h (p 211) lists the prototypes |
for the Result::Result constructor and the Result::~Result destructor |
Anonymous | |
Printed | Page 212 1st paragraph, 3rd sentence: "simple" should be "simply". |
Anonymous | ||
Printed | Page 215 It is stated that "an example application using these |
C++ classes is packaged with the examples from this book". I cannot find |
Anonymous | |
Printed | Page 227 The 1st paragraph after the heading 'A Guest Book Servlet' mentions that |
"we have packaged with the examples in this book an example that contains a |
Anonymous | |
Printed | Page 227 The book I just purchased is missing part of page 227 (after the |
second paragraph) and pages 228, 229, and 230. |
Anonymous | |
Printed | Page 231 2nd-to-last ALTER example: "table" and "create_clause" should be |
italicized like the rest of them. |
Anonymous | |
Printed | Page 234 2nd paragraph under "CREATE", 2nd sentence: "In older versions of |
SQL..." should be "In older versions of MySQL..." |
Anonymous | |
Printed | Page 237 There is a syntax mistake on page 237 in the comment column for |
ENUM. The line reads: |
Anonymous | |
Printed | Page 243 In the last line of the DESCRIBE / DESC, |
The book shows: |
Anonymous | |
Printed | Page 245 for the list of privileges to GRANT, the first one is misspelled |
and should be "ALL PRIVILEGES/ALL". |
Anonymous | |
Printed | Page 247 The code lines |
INSERT INTO old_data ( id, date, field ) SELECT ( id, date, field) |
Anonymous | |
Printed | Page 249 |
Your description of LOCK TABLES on page 249 states that if a thread: |
Anonymous | |
Printed | Page 249 I have found what I believe to be a serious error in the description |
of the LOCK query for MySQL. Under the heading LOCK, the second |
Anonymous | |
Printed | Page 251 The penultimate paragraph currently reads: |
"[about OPTIONALLY] This will cause MySQL to thread |
Anonymous | |
Printed | Page 252 The third join example, under Table LEFT [OUTER] JOIN Table2 |
ON clause, reads: |
Anonymous | |
Printed | Page 253 the list of operators for WHERE statements appear to be in an |
italic font. It would look better in a normal font. |
Anonymous | |
Printed | Page 254-255 In the GROUP BY and ORDER BY clauses, the columns shouldn't |
be given as a column-name; it is also possible to give the column-number |
Anonymous | |
Printed | Page 259 |
The e.g. currently reads: |
Anonymous | |
Printed | Page 259 4th function definition |
BOOK EXTRACT :- |
Anonymous | |
Printed | Page 259 last line |
time for a singe session. Running GET_LOCK() ... |
Anonymous | |
Printed | Page 306 Chapter 18, "dexhex" The glossary term "dexhex" should be |
changed to "dechex" (as in 'decimal to hexidecimal'). |
Anonymous | |
Printed | Page 323 mysql_listtables() |
should be: |
Anonymous | |
Printed | Page 378 Example code for using DBI::bind_columns |
$myothertable_output->bind_columns(undef, ($name, $date)); is called |
Anonymous | |
Printed | Page 382 DBI::do and DBI::disconnect are out of order alphabetically. |
Anonymous | ||
Printed | Page 384 Example code for DBI::execute |
The last "paragraph" of code in the example calls |
Anonymous | |
Printed | Page 386 Section: DBI::fetchrow_hashref |
The example code for this command is incorrect. The incorrect example |
Anonymous | |
Printed | Page 413 The example code started on p. 412 should show the use of |
Mysql::errno. To do this the, following line on p. 413 has to be changed. |
Anonymous | |
Printed | Page 472 Change: |
"DATE datatype, 72, 95, 236, 270" |
Anonymous | |
Printed | Page 486 Index: Change |
|
Anonymous | |
Printed | Page 486 'UPDATE statement' points to page 269. |
However, the update statement is on page 268. |
Anonymous |