diff --git a/Docs/manual.texi b/Docs/manual.texi index e6d28b8a9c6..7d3fcb69a7c 100644 --- a/Docs/manual.texi +++ b/Docs/manual.texi @@ -3234,7 +3234,7 @@ In MySQL Server 4.0 you can use multi-table delete to delete rows from many tables with one command. @xref{DELETE}. In the near future we will extend the @code{FOREIGN KEY} implementation -so that the information will be saved in the table specification file +so that the information will be saved in the table-specification file and may be retrieved by @code{mysqldump} and ODBC. At a later stage we will implement the foreign key constraints for applications that can't easily be coded to avoid them. @@ -7971,7 +7971,7 @@ If you are using InnoDB tables, refer to the InnoDB-specific startup options. @xref{InnoDB start}. If you are using BDB (Berkeley DB) tables, you should familiarise -yourself with the different BDB specific startup options. @xref{BDB start}. +yourself with the different BDB-specific startup options. @xref{BDB start}. @node Automatic start, , Starting server, Post-installation @@ -8328,7 +8328,7 @@ link and the original database are deleted. (This didn't happen in 3.22 because configure didn't detect the @code{readlink} system call.) @item -@code{OPTIMIZE TABLE} now only works for @code{MyISAM} tables. +@code{OPTIMIZE TABLE} now works only for @code{MyISAM} tables. For other table types, you can use @code{ALTER TABLE} to optimise the table. During @code{OPTIMIZE TABLE} the table is now locked from other threads. @@ -13419,7 +13419,7 @@ WHERE price=19.95 @end enumerate Another solution is to sort all rows descending by price and only -get the first row using the MySQL specific @code{LIMIT} clause: +get the first row using the MySQL-specific @code{LIMIT} clause: @example SELECT article, dealer, price @@ -17753,7 +17753,7 @@ BACKUP TABLE tbl_name[,tbl_name...] TO '/path/to/backup/directory' Copies to the backup directory the minimum number of table files needed to restore the table, after flushing any buffered changes to disk. Currently -only works for @code{MyISAM} tables. +works only for @code{MyISAM} tables. For @code{MyISAM} tables, copies @file{.frm} (definition) and @file{.MYD} (data) files. The index file can be rebuilt from those two. @@ -17817,7 +17817,7 @@ CHECK TABLE tbl_name[,tbl_name...] [option [option...]] option = QUICK | FAST | MEDIUM | EXTENDED | CHANGED @end example -@code{CHECK TABLE} only works on @code{MyISAM} and @code{InnoDB} tables. On +@code{CHECK TABLE} works only on @code{MyISAM} and @code{InnoDB} tables. On @code{MyISAM} tables it's the same thing as running @code{myisamchk -m table_name} on the table. @@ -17924,7 +17924,7 @@ to set the column to some other value than 0. REPAIR TABLE tbl_name[,tbl_name...] [QUICK] [EXTENDED] [USE_FRM] @end example -@code{REPAIR TABLE} only works on @code{MyISAM} tables and is the same +@code{REPAIR TABLE} works only on @code{MyISAM} tables and is the same as running @code{myisamchk -r table_name} on the table. Normally you should never have to run this command, but if disaster strikes @@ -17955,7 +17955,7 @@ If @code{QUICK} is given then MySQL will try to do a If you use @code{EXTENDED} then MySQL will create the index row by row instead of creating one index at a time with sorting; this may be -better than sorting on fixed-length keys if you have long @code{char()} +better than sorting on fixed-length keys if you have long @code{CHAR} keys that compress very good. As of @code{MySQL} 4.0.2 there is a @code{USE_FRM} mode for @code{REPAIR}. @@ -19127,7 +19127,7 @@ Deleted records are maintained in a linked list and subsequent @code{INSERT} operations reuse old record positions. You can use @code{OPTIMIZE TABLE} to reclaim the unused space and to defragment the datafile. -For the moment, @code{OPTIMIZE TABLE} only works on @code{MyISAM} and +For the moment, @code{OPTIMIZE TABLE} works only on @code{MyISAM} and @code{BDB} tables. For @code{BDB} tables, @code{OPTIMIZE TABLE} is currently mapped to @code{ANALYZE TABLE}. @xref{ANALYZE TABLE, , @code{ANALYZE TABLE}}. @@ -19306,7 +19306,7 @@ Otherwise, you can only see and kill your own threads. You can also use the @code{mysqladmin processlist} and @code{mysqladmin kill} commands to examine and kill threads. -When you do a @code{KILL}, a thread specific @code{kill flag} is set for +When you do a @code{KILL}, a thread-specific @code{kill flag} is set for the thread. In most cases it may take some time for the thread to die as the kill @@ -20188,7 +20188,7 @@ want to increase this value. @item @code{record_rnd_buffer_size} When reading rows in sorted order after a sort, the rows are read through this buffer to avoid a disk seeks. Can improve @code{ORDER BY} -by a lot if set to a high value. As this is a thread specific variable, +by a lot if set to a high value. As this is a thread-specific variable, one should not set this big globally, but just change this when running some specific big queries. @@ -28613,15 +28613,16 @@ Starting from MySQL 4.0.3 we provide better access to a lot of system and connection variables. One can change most of them without having to take down the server. -There are two kind of system variables: Thread (or connection) specific +There are two kind of system variables: Thread-specific (or +connection-specific) variables that are unique to the current connection and global variables that are either used to configure global events or used as initial variables for a new connection. When mysqld starts all global variables are initialised from command line arguments and option files. You can change the used value with the -@code{SET GLOBAL} command. When a new thread is created the thread -specific variables are initialised from the global variables and they +@code{SET GLOBAL} command. When a new thread is created the thread-specific +variables are initialised from the global variables and they will not change even if one issues a new @code{SET GLOBAL} command. To set the value for a @code{GLOBAL} variable, you should use one @@ -28665,14 +28666,14 @@ SHOW SESSION VARIABLES like 'sort_buffer_size'; When you @strong{retrieve} a variable value with the @code{@@@@variable_name} syntax and you don't specify @code{GLOBAL} or -@code{SESSION} then MySQL will return the thread specific +@code{SESSION} then MySQL will return the thread-specific (@code{SESSION}) value if it exists. If not, MySQL will return the global value. The reason for requiring @code{GLOBAL} for setting @code{GLOBAL} only variables but not for retrieving them is to ensure that we don't later -run into problems if we later would introduce a thread specific variable -with the same name or remove a thread specific variable. In this case +run into problems if we later would introduce a thread-specific variable +with the same name or remove a thread-specific variable. In this case you could accidently change the state for the whole server and not just for your own connection. @@ -44836,7 +44837,7 @@ None. @subsubheading Description This function needs to be called for each created thread to initialise -thread specific variables. +thread-specific variables. This is automatically called by @code{my_init()} and @code{mysql_connect()}. @@ -45226,12 +45227,12 @@ MySQL functions which did not create the connection to the MySQL database: When you call @code{mysql_init()} or @code{mysql_connect()}, MySQL will -create a thread specific variable for the thread that is used by the +create a thread-specific variable for the thread that is used by the debug library (among other things). If you call a MySQL function, before the thread has called @code{mysql_init()} or @code{mysql_connect()}, the thread will -not have the necessary thread specific variables in place and you are +not have the necessary thread-specific variables in place and you are likely to end up with a core dump sooner or later. The get things to work smoothly you have to do the following: @@ -45245,8 +45246,8 @@ Call @code{mysql_thread_init()} in the thread handler before calling any MySQL function. @item In the thread, call @code{mysql_thread_end()} before calling -@code{pthread_exit()}. This will free the memory used by MySQL thread -specific variables. +@code{pthread_exit()}. This will free the memory used by MySQL +thread-specific variables. @end enumerate You may get some errors because of undefined symbols when linking your @@ -45352,11 +45353,11 @@ embedded. @xref{Option files}. Put common options in the @code{[server]} section. These will be read by both MySQL versions. @item -Put client/server specific options in the @code{[mysqld]} section. +Put client/server-specific options in the @code{[mysqld]} section. @item -Put embedded MySQL specific options in the @code{[embedded]} section. +Put embedded MySQL-specific options in the @code{[embedded]} section. @item -Put application specific options in a @code{[ApplicationName_SERVER]} +Put application-specific options in a @code{[ApplicationName_SERVER]} section. @end itemize @@ -50433,7 +50434,7 @@ Fixed client hangup bug when using some SQL commands with wrong syntax. @item Fixed a timing bug in @code{DROP DATABASE} @item -New @code{SET [GLOBAL | SESSION]} syntax to change thread specific and global +New @code{SET [GLOBAL | SESSION]} syntax to change thread-specific and global server variables at runtime. @item Added variable @code{slave_compressed_protocol}.