Late source entry of some proofread catches in ch02.

parent db8610b3
......@@ -6929,7 +6929,7 @@ install MySQL, create some tables, then reconfigure
MySQL to use a different character set and reinstall it.)
With the option @code{--with-extra-charset=LIST} you can define
which additional character sets should be incompiled in the server.
which additional character sets should be compiled into the server.
Here @code{LIST} is either a list of character
sets separated with spaces,
......@@ -8139,7 +8139,7 @@ version 4.0;
@code{UNSIGNED} flag on storage (before, @code{UNSIGNED} was ignored for
these columns).
@item
Use @code{ORDER BY column DESC} now always sorts @code{NULL} values
@code{ORDER BY column DESC} now always sorts @code{NULL} values
first; in 3.23 this was not always consistent.
@item
@code{SHOW INDEX} has 2 columns more (@code{Null} and @code{Index_type})
......@@ -8188,8 +8188,8 @@ it is preferable to change the client to use the new 4.0 API.
@item
In the @code{MYSQL_FIELD} structure, @code{length} and @code{max_length} have
changed from @code{unsigned int} to @code{unsigned long}. This should not
cause any other problems than some warnings if you use these to
@code{printf()} type function.
cause any problems, except that they may generate warning messages when
used as arguments in the @code{printf()} class of functions.
@item
You should use @code{TRUNCATE TABLE} when you want to delete all rows
from a table and you don't care how many rows were deleted.
......@@ -8315,8 +8315,8 @@ MySQL Version 3.22 and Version 3.23, you should not use the
@item
Check all your calls to @code{DATE_FORMAT()} to make sure there is a
@samp{%} before each format character. (Later MySQL Version 3.22
did allow this syntax.)
@samp{%} before each format character.
(MySQL Version 3.22 and later already allowed this syntax.)
@item
@code{mysql_fetch_fields_direct} is now a function (it was a macro) and
......@@ -8986,8 +8986,8 @@ You can avoid using @file{libg++.a} by running @code{configure} like this:
shell> CXX=gcc ./configure
@end example
If you are running gcc 3.0 and above, you can't use the above trick with
setting to CXX=gcc.
If you are running gcc 3.0 or above, you can't use the aforementioned trick
of setting CXX=gcc.
@node Linux-SPARC, Linux-Alpha, Linux-x86, Linux
@subsubsection Linux SPARC Notes
......@@ -9078,7 +9078,7 @@ work). You must also use the @code{egcs} C++ compiler
@node Linux-IA64, , Linux-MIPS, Linux
@subsubsection Linux IA64 Notes
To get MySQL to compile on Linux Ia64, we use the following compile line:
To get MySQL to compile on Linux IA64, we use the following compile line:
Using @code{gcc-2.96}:
@example
......@@ -9088,7 +9088,7 @@ CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \
"--with-comment=Official MySQL binary" --with-extra-charsets=complex
@end example
On Ia64 the MySQL client binaries are using shared libraries. This means
On IA64 the MySQL client binaries are using shared libraries. This means
that if you install our binary distribution in some other place than
@file{/usr/local/mysql} you need to either modify @file{/etc/ld.so.conf}
or add the path to the directory where you have @file{libmysqlclient.so}
......@@ -9368,8 +9368,9 @@ C:\> mysqladmin --user=root --password=your_password shutdown
If you are using the old shareware version of MySQL Version
3.21 under Windows, the above command will fail with an error:
@code{parse error near 'SET OPTION password'}. The fix is in to upgrade
to the current MySQL version, which is freely available.
@code{parse error near 'SET OPTION password'}. The solution for
this is to download and upgrade to the latest MySQL version,
which is now freely available.
With the current MySQL versions you can easily add new users
and change privileges with @code{GRANT} and @code{REVOKE} commands.
......@@ -10402,7 +10403,7 @@ PHKL_22840 Streams cumulative
PHNE_22397 ARPA cumulative
@end example
This will solve a problem that one gets @code{EWOULDBLOCK} from @code{recv()}
This will solve the problem of getting @code{EWOULDBLOCK} from @code{recv()}
and @code{EBADF} from @code{accept()} in threaded applications.
If you are using @code{gcc} 2.95.1 on an unpatched HP-UX 11.x system,
......@@ -21535,7 +21536,7 @@ binaries includes:
@item HP-UX 11.0 @tab N @tab Y
@item Linux-Alpha @tab N @tab Y
@item Linux-Intel @tab Y @tab Y
@item Linux-Ia64 @tab N @tab Y
@item Linux-IA64 @tab N @tab Y
@item Solaris-Intel @tab N @tab Y
@item Solaris-SPARC @tab Y @tab Y
@item Caldera (SCO) OSR5 @tab Y @tab Y
......@@ -51237,7 +51238,7 @@ Fixed that open transactions in @code{BDB} tables are rolled back if the
connection is closed unexpectedly.
@item
Added workaround for a bug in @code{gcc} 2.96 (intel) and @code{gcc} 2.9
(Ia64) in @code{gen_lex_hash.c}.
(IA64) in @code{gen_lex_hash.c}.
@item
Fixed memory leak in the client library when using @code{host=} in the
@file{my.cnf} file.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment