Fixup of some titles (length and caps).

* Tutorial::                    MySQL Tutorial

* MySQL Database Administration::  MySQL Database Administration

* MySQL Optimisation::          MySQL Optimisation

* Reference::                   MySQL language reference

* Table types::                 MySQL table types

* Clients::                     MySQL client tools and APIs

* Reference::                   MySQL Language Reference

* Table types::                 MySQL Table Types

* Clients::                     MySQL Client Tools and APIs

* Extending MySQL::             Extending MySQL

* Problems::                    Problems

* Contrib::                     Contributed programs

* Contrib::                     Contributed Programs

* Credits::                     Contributors to MySQL

* News::                        MySQL change history

* Porting::                     Comments on porting to other systems

* News::                        MySQL Change History

* Porting::                     Porting to Other Systems

* Environment variables::       MySQL environment variables

* Regexp::                      Description of MySQL regular expression syntax

* Regexp::                      MySQL Regular Expression Syntax

* GPL license::                 GNU General Public License

* LGPL license::                GNU Lesser General Public License

* Function Index::              SQL command, type and function index

* Function Index::              SQL Command, Type and Function Index

* Concept Index::               Concept Index

@end menu

@node Tutorial, MySQL Database Administration, Installing, Top

@chapter Introduction to MySQL: A MySQL Tutorial

@chapter Tutorial Introduction to MySQL

@cindex tutorial

@cindex terminal monitor, defined

@node Can not connect to server, Blocked host, Gone away, Common errors

@appendixsubsec @code{Can't connect to [local] MySQL server} error

@appendixsubsec @code{Can't connect to [local] MySQL server} Error

A MySQL client on Unix can connect to the @code{mysqld} server in two

different ways: Unix sockets, which connect through a file in the file

@node Problems with mysql.sock, Timezone problems, Temporary files, Administration Issues

@appendixsubsec How to Protect or change the MySQL socket file @file{/tmp/mysql.sock}

@appendixsubsec How to Protect or Change the MySQL Socket File @file{/tmp/mysql.sock}

@cindex @code{mysql.sock}, protection

@cindex deletion, @code{mysql.sock}

@end enumerate

@node Problems with float,  , No matching rows, Query Issues

@appendixsubsec Problems with floating point comparison

@appendixsubsec Problems with Floating Point Comparison

Floating point numbers cause confusion sometimes, because these numbers

are not stored as exact values inside computer architecture. What one

@node News, Porting, Credits, Top

@appendix MySQL change history

@appendix MySQL Change History

@cindex ChangeLog

@cindex changes, log

@node Porting, Environment variables, News, Top

@appendix Comments on Porting to Other Systems

@appendix Porting to Other Systems

@cindex porting, to other systems

@menu

* Debugging server::            Debugging a MySQL server

* Debugging client::            Debugging a MySQL client

* The DBUG package::            The DBUG package

* Locking methods::             Locking methods

* The DBUG package::            The DBUG Package

* Locking methods::             Locking ethods

* RTS-threads::                 Comments about RTS threads

* Thread packages::             Differences between different thread packages

@end menu

@node Compiling for debugging, Making trace files, Debugging server, Debugging server

@appendixsubsec Compiling MYSQL for debugging

@appendixsubsec Compiling MYSQL for Debugging

If you have some very specific problem, you can always try to debug

MySQL.  To do this you must configure MySQL with the

@node Making trace files, Using gdb on mysqld, Compiling for debugging, Debugging server

@appendixsubsec Creating trace files

@appendixsubsec Creating Trace Files

If the @code{mysqld} server doesn't start or if you can cause the

@code{mysqld} server to crash quickly, you can try to create a trace

@node Using stack trace, Using log files, Using gdb on mysqld, Debugging server

@appendixsubsec Using a stack trace

@appendixsubsec Using a Stack Trace

On some operating systems, the error log will contain a stack trace if

@code{mysqld} dies unexpectedly. You can use this to find out where (and

@node Using log files, Reproduceable test case, Using stack trace, Debugging server

@appendixsubsec Using log files to find cause of errors in mysqld

@appendixsubsec Using Log Files to Find Cause of Errors in mysqld

Note that before starting @code{mysqld} with @code{--log} you should

check all your tables with @code{myisamchk}.

@node Reproduceable test case,  , Using log files, Debugging server

@appendixsubsec Making a test case when you experience table corruption

@appendixsubsec Making a Test Case When You Experience Table Corruption

If you get corrupted tables or if @code{mysqld} always fails after some

update commands, you can test if this bug is reproducible by doing the

@node The DBUG package, Locking methods, Debugging client, Porting

@appendixsec The DBUG package.

@appendixsec The DBUG Package

@cindex DBUG package

@node Regexp, GPL license, Environment variables, Top

@appendix Description of MySQL regular expression syntax

@appendix MySQL Regular Expression Syntax

@cindex regex

@cindex regular expression syntax, described

@node LGPL license, Function Index, GPL license, Top

@appendix GNU LESSER GENERAL PUBLIC LICENSE

@cindex LGPL, Lesser General Public License

@cindex LGPL, Library General Public License

@cindex LGPL, GNU Library General Public License

@cindex LGPL, Lesser General Public License

@cindex LGPL, GNU Lesser General Public License

@center Version 2.1, February 1999