diff options
Diffstat (limited to 'Docs/manual.texi')
| -rw-r--r-- | Docs/manual.texi | 258 |
1 files changed, 165 insertions, 93 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi index 1c6b31d9af2..51a40019f1e 100644 --- a/Docs/manual.texi +++ b/Docs/manual.texi @@ -1052,8 +1052,8 @@ tricky questions are answered by Michael @code{Monty} Widenius, principal author of the @code{MySQL Server}. @xref{Support}. -To order support at various levels, please visit the order section at -@uref{https://order.mysql.com/} or contact our sales staff at +For more information and ordering support at various levels, see +@uref{http://www.mysql.com/support/} or contact our sales staff at @email{sales@@mysql.com}. @@ -1138,7 +1138,8 @@ This means that the @code{MySQL} software can be used free of charge under the @code{GPL}. If you do not want to be bound by the @code{GPL} terms (like the requirement that your own application becomes @code{GPL} as well), you may purchase a commercial license for the same product -from @code{MySQL AB} at @uref{https://order.mysql.com/}. +from @code{MySQL AB}. +See @uref{http://www.mysql.com/support/arrangements/price.html}. Since @code{MySQL AB} owns the copyright to the @code{MySQL} source code, we are able to employ @code{Dual Licensing} which means that the same product is available under @code{GPL} and under a commercial @@ -1208,9 +1209,8 @@ For press service and inquiries not covered in our News releases If you have a valid support contract with @code{MySQL AB}, you will get timely, precise answers to your technical questions about the @code{MySQL} software. For more information, see @ref{Support}. -You can order your support contract at -@uref{https://order.mysql.com/}, or send an e-mail message to -@email{sales@@mysql.com}. +On our website, see @uref{http://www.mysql.com/support/}, or send +an e-mail message to @email{sales@@mysql.com}. For information about @code{MySQL} training, please visit the training section at @uref{http://www.mysql.com/training/}. If you have @@ -1230,7 +1230,10 @@ consulting staff at @email{consulting@@mysql.com}. Commercial licenses may be purchased online at @uref{https://order.mysql.com/}. There you will also find information -on how to fax your purchase order to @code{MySQL AB}. If you have +on how to fax your purchase order to @code{MySQL AB}. More information +about licensing can be found at +@uref{http://www.mysql.com/support/arrangements/price.html}. +If you have questions regarding licensing or you want a quote for a high-volume license deal, please fill in the contact form on our web site (@uref{http://www.mysql.com/}) or send an e-mail message @@ -1334,7 +1337,7 @@ not third-party products that access the @code{MySQL} server, though we try to help with these where we can. Detailed information about our various support options is given at -@uref{https://order.mysql.com/}, where support contracts can also be +@uref{http://www.mysql.com/support/}, where support contracts can also be ordered online. If you have restricted access to the Internet, contact our sales staff at @email{sales@@mysql.com}. @@ -1430,6 +1433,8 @@ Since the @code{MySQL} software is released under the @code{GPL}, it may often be used for free, but for certain uses you may want or need to buy commercial licenses from @code{MySQL AB} at @uref{https://order.mysql.com/}. +See @uref{http://www.mysql.com/support/arrangements.html} for +more information. Older versions of @code{MySQL} (3.22 and earlier) are subject to a more strict license @@ -1490,10 +1495,11 @@ If you require a license, you will need one for each installation of the is no artificial limit on the number of clients that connect to the server in any way. -To purchase commercial licenses and support, please visit the order section -of our web site at @uref{https://order.mysql.com/}. If you have special -licensing needs or you have restricted access to the Internet, please contact -our sales staff at @email{sales@@mysql.com}. +For commercial licenses, please visit our website at +@uref{http://www.mysql.com/support/arrangements/price.html}. +For support contracts, see @uref{http://www.mysql.com/support/}. +If you have special needs or you have restricted access to the Internet, +please contact our sales staff at @email{sales@@mysql.com}. @node Using the MySQL software for free under GPL, , Using the MySQL software under a commercial license, MySQL licenses @@ -1726,7 +1732,7 @@ Other new features target the users of embedded databases. The rollout of MySQL Server 4.x comes in several steps, with the first version labelled 4.0.0-alpha already containing most of the new features. Additional features have since been incorporated into -MySQL 4.0.1, 4.0.2, and onward; Now, MySQL 4.0 will be labelled beta. +MySQL 4.0.1, 4.0.2, and onward; MySQL 4.0.3 has been labelled beta. Further new features are being added in MySQL 4.1, targeted for alpha release in third quarter 2002. @@ -1735,7 +1741,8 @@ alpha release in third quarter 2002. @subsection Ready for Immediate Development Use Users are not recommended to switch their production systems -to MySQL Server 4.x until it is released in beta version. +to a MySQL Server 4.x until it is released in beta version +(such as 4.0.3 beta). However, even the initial release has passed our extensive test suite without any errors on any of the platforms we test on. Due to the large number of new features, we thus recommend @@ -1780,20 +1787,6 @@ standard MySQL server, including full support for @code{transactions} and @code{row-level locking}. @item -MySQL Server 4.0 supports secure traffic between the client and the server, -greatly increasing security against malicious intrusion and unauthorised -access. Web applications being a cornerstone of MySQL use, web developers -have been able to use @code{Secure Socket Layer} (@code{SSL}) to secure the -traffic between the the end user browser and the web application, be it -written in PHP, Perl, ASP or using any other web development tool. However, -the traffic between the development tool and the @code{mysqld} server -process has been protected only by virtue of them being processes -residing on computers within the same firewall. In MySQL Server 4.0, -the @code{mysqld} server daemon process can itself use @code{SSL}, -thus enabling secure traffic to MySQL databases from, say, a Windows -application residing outside the firewall. - -@item Our German, Austrian, and Swiss users will note that we have a new character set, @code{latin_de}, which corrects the @emph{German sorting order}, placing German umlauts in the same order as German telephone books. @@ -6929,7 +6922,7 @@ system-specific section of this manual. @cindex development source tree @cindex BitKeeper tree -@cindex cvs tree +@cindex CVS tree @strong{Caution}: You should read this section only if you are interested in helping us test our new code. If you just want to get MySQL up @@ -7020,7 +7013,7 @@ should run @code{bk pull} periodically to get the updates. You can examine the change history for the tree with all the diffs by using @code{bk sccstool}. If you see some funny diffs or code that you have a question about, do not hesitate to send e-mail to -@email{internals@@lists.mysql.com}. Also, if you think you have a better idea +@email{internals@@lists.mysql.com}. Also, if you think you have a better idea on how to do something, send an e-mail to the same address with a patch. @code{bk diffs} will produce a patch for you after you have made changes to the source. If you do not have the time to code your idea, just send @@ -7030,6 +7023,15 @@ a description. @code{BitKeeper} has a nice help utility that you can access via @code{bk helptool}. +@item +Please note that any commits (@code{bk ci} or @code{bk citool}) will +trigger the posting of a message with the changeset to our internals +mailing list, as well as the usual openlogging.org submission with +just the changeset comments. +Generally, you wouldn't need to use commit (since the public tree will +not allow @code{bk push}), but rather use the @code{bk diffs} method +described previously. + @end enumerate @@ -20067,14 +20069,16 @@ If the temporary file used for fast index creation would be bigger than using the key cache by the amount specified here, then prefer the key cache method. This is mainly used to force long character keys in large tables to use the slower key cache method to create the index. -@strong{Note} that this parameter is given in megabytes! +@strong{Note} that this parameter is given in megabytes before 4.0.3 and +in bytes starting from this version. @item @code{myisam_max_sort_file_size} The maximum size of the temporary file MySQL is allowed to use while recreating the index (during @code{REPAIR}, @code{ALTER TABLE} or @code{LOAD DATA INFILE}. If the file-size would be bigger than this, the index will be created through the key cache (which is slower). -@strong{Note} that this parameter is given in megabytes! +@strong{Note} that this parameter is given in megabytes before 4.0.3 and +in bytes starting from this version. @item @code{net_buffer_length} The communication buffer is reset to this size between queries. This @@ -23168,10 +23172,10 @@ exactly what @code{mysqld} thought the client sent to it. @c Note: this instance of "safe_mysql" should not be changed to "mysqld_safe" @c because it's a 3.23.x-specific command Older versions of the @code{mysql.server} script (from MySQL 3.23.4 to 3.23.8) -pass @code{safe_mysqld} a @code{--log} option. If you need better performance -when you start using MySQL in a production environment, you can remove the -@code{--log} option from @code{mysql.server} or change it to -@code{--log-bin}. +pass @code{safe_mysqld} a @code{--log} option (enable general query log). +If you need better performance when you start using MySQL in a production +environment, you can remove the @code{--log} option from @code{mysql.server} +or change it to @code{--log-bin}. @xref{Binary log}. The entries in this log are written as @code{mysqld} receives the questions. This may be different from the order in which the statements are executed. @@ -23250,7 +23254,9 @@ we recommend you to switch to this log format as soon as possible! The binary log contains all information that is available in the update log in a more efficient format. It also contains information about how long -every query that updated the database took. +every query that updated the database took. It doesn't contain queries that +doesn't modify any data. If you want to log all queries (for example to +find a problem query) you should use the general query log. @xref{Query log}. The binary log is also used when you are replicating a slave from a master. @xref{Replication}. @@ -23822,7 +23828,8 @@ the slave to apply updates from one database on the master to the one with a different name on the slave. @item Starting in Version 3.23.28, you can use @code{PURGE MASTER LOGS TO 'log-name'} -to get rid of old logs while the slave is running. +to get rid of old logs while the slave is running. This will remove all old +logs before, but not including @code{'log-name'}. @item Due to the non-transactional nature of MyISAM tables, it is possible to have a query that will only partially update a table and return an error code. This @@ -23855,7 +23862,6 @@ above bugs are conceptually very simple to fix, we have not yet found a way to do this without a sigficant code change that would compromize the stability status of 3.23 branch. There exists a workaround for both if in the rare case it happens to affect your application -- use @code{slave-skip-errors}. - @end itemize @@ -24125,6 +24131,10 @@ Example: Tells the slave server not to start the slave on the startup. The user can start it later with @code{SLAVE START}. +@item @code{slave_compressed_protocol=#} @tab +If 1, then use compression on the slave/client protocol if both +slave and master supports this. + @item @code{slave_net_timeout=#} @tab Number of seconds to wait for more data from the master before aborting the read. @@ -28622,6 +28632,7 @@ and if you can use @code{GLOBAL} or @code{SESSION} with them. @item delayed_queue_size @tab num @tab GLOBAL @item flush @tab bool @tab GLOBAL @item flush_time @tab num @tab GLOBAL +@item foreign_key_checks @tab bool @tab SESSION @item identity @tab num @tab SESSION @item insert_id @tab bool @tab SESSION @item interactive_timeout @tab num @tab GLOBAL | SESSION @@ -28658,6 +28669,7 @@ and if you can use @code{GLOBAL} or @code{SESSION} with them. @item rpl_recovery_rank @tab num @tab GLOBAL @item safe_show_database @tab bool @tab GLOBAL @item server_id @tab num @tab GLOBAL +@item slave_compressed_protocol @tab bool @tab GLOBAL @item slave_net_timeout @tab num @tab GLOBAL @item slow_launch_time @tab num @tab GLOBAL @item sort_buffer_size @tab num @tab GLOBAL | SESSION @@ -28683,6 +28695,7 @@ and if you can use @code{GLOBAL} or @code{SESSION} with them. @item tx_isolation @tab enum @tab GLOBAL | SESSION @item version @tab string @tab GLOBAL @item wait_timeout @tab num @tab GLOBAL | SESSION +@item unique_checks @tab bool @tab SESSION @end multitable Variables that are marked with @code{num} can be given a numerical @@ -29486,6 +29499,17 @@ Conversions that occur due to clipping are reported as ``warnings'' for @code{ALTER TABLE}, @code{LOAD DATA INFILE}, @code{UPDATE}, and multi-row @code{INSERT} statements. +@c FIX arjen 2002-08-07 New table, not yet measured for O'Reilly/DocBook +@c FIX also need to shuffle into proper position and adjust text. +@multitable @columnfractions .20 .20 .30 .30 +@item @strong{Type} @tab @strong{Bytes} @tab @strong{From} @tab @strong{To} +@item @code{TINYINT} @tab 1 @tab -128 @tab 127 +@item @code{SMALLINT} @tab 2 @tab -32768 @tab 32767 +@item @code{MEDIUMINT} @tab 3 @tab -8388608 @tab 8388607 +@item @code{INT} @tab 4 @tab -2147483648 @tab 2147483647 +@item @code{BIGINT} @tab 8 @tab -9223372036854775808 @tab 9223372036854775807 +@end multitable + @node Date and time types, String types, Numeric types, Column types @subsection Date and Time Types @@ -30016,6 +30040,16 @@ The string types are @code{CHAR}, @code{VARCHAR}, @code{BLOB}, @code{TEXT}, @code{ENUM}, and @code{SET}. This section describes how these types work, their storage requirements, and how to use them in your queries. +@c FIX arjen 2002-08-07 New table, not yet measured for O'Reilly/DocBook +@c FIX also need to shuffle into proper position and adjust text. +@multitable @columnfractions .40 .30 .30 +@item @strong{Type} @tab @strong{Max.size} @tab @strong{Bytes} +@item @code{TINYTEXT} or @code{TINYBLOB} @tab 2^8-1 @tab 255 +@item @code{TEXT} or @code{BLOB} @tab 2^16-1 (64K-1) @tab 65535 +@item @code{MEDIUMTEXT} or @code{MEDIUMBLOB} @tab 2^24-1 (16M-1) @tab 16777215 +@item @code{LONGBLOB} @tab 2^32-1 (4G-1) @tab 4294967295 +@end multitable + @node CHAR, BLOB, String types, String types @subsubsection The @code{CHAR} and @code{VARCHAR} Types @@ -37293,8 +37327,9 @@ of the form @code{SELECT * FROM AUTOINCREMENT_FIELD IS NULL} However, @code{FOUND ROWS()} will return the correct value, even if the preceding query was fetched from the cache. -Queries that don't use any tables or if the user has a column privilege for -any of the involved tables are not cached. +In case a query does not use any tables, or uses temporary tables, +or if the user has a column privilege for any of the involved tables, +that query will not be cached. Before a query is fetched from the query cache, MySQL will check that the user has SELECT privilege to all the involved databases and @@ -37615,8 +37650,8 @@ The following options to @code{mysqld} can be used to change the behaviour of @item @code{--myisam-recover=#} @tab Automatic recovery of crashed tables. @item @code{-O myisam_sort_buffer_size=#} @tab Buffer used when recovering tables. @item @code{--delay-key-write-for-all-tables} @tab Don't flush key buffers between writes for any MyISAM table -@item @code{-O myisam_max_extra_sort_file_size=#} @tab Used to help MySQL to decide when to use the slow but safe key cache index create method. @strong{Note} that this parameter is given in megabytes! -@item @code{-O myisam_max_sort_file_size=#} @tab Don't use the fast sort index method to created index if the temporary file would get bigger than this. @strong{Note} that this paramter is given in megabytes! +@item @code{-O myisam_max_extra_sort_file_size=#} @tab Used to help MySQL to decide when to use the slow but safe key cache index create method. @strong{Note} that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version. +@item @code{-O myisam_max_sort_file_size=#} @tab Don't use the fast sort index method to created index if the temporary file would get bigger than this. @strong{Note} that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version. @item @code{-O bulk_insert_buffer_size=#} @tab Size of tree cache used in bulk insert optimisation. @strong{Note} that this is a limit @strong{per thread}! @end multitable @@ -49712,7 +49747,7 @@ The MySQL Certification program. @item Lenz Grimmer @itemize @bullet @item -Build and release engineering. +Production (build and release) engineering. @end itemize @item Peter Zaitsev @@ -50056,7 +50091,7 @@ this means that the version has not yet been released! @c Please don't add a new version here without also updating ../configure.in! @menu -* News-4.0.x:: Changes in release 4.0.x (Development; Alpha) +* News-4.0.x:: Changes in release 4.0.x (Beta) * News-3.23.x:: Changes in release 3.23.x (Stable) * News-3.22.x:: Changes in release 3.22.x (Older; Still supported) * News-3.21.x:: Changes in release 3.21.x @@ -50066,7 +50101,7 @@ this means that the version has not yet been released! @node News-4.0.x, News-3.23.x, News, News -@appendixsec Changes in release 4.0.x (Development; Alpha) +@appendixsec Changes in release 4.0.x (Beta) @cindex changes, version 4.0 @@ -50124,20 +50159,38 @@ each individual 4.0.x release. @menu -* News-4.0.3:: Changes in release 4.0.3 -* News-4.0.2:: Changes in release 4.0.2 (01 July 2002) +* News-4.0.3:: Changes in release 4.0.3 (Aug 2002: Beta) +* News-4.0.2:: Changes in release 4.0.2 (01 Jul 2002) * News-4.0.1:: Changes in release 4.0.1 (23 Dec 2001) * News-4.0.0:: Changes in release 4.0.0 (Oct 2001: Alpha) @end menu @node News-4.0.3, News-4.0.2, News-4.0.x, News-4.0.x -@appendixsubsec Changes in release 4.0.3 +@appendixsubsec Changes in release 4.0.3 (Aug 2002: Beta) @itemize @bullet @item mysqld now has the option @code{--temp-pool} enabled by default as this gives better performance with some OS. @item +Big code cleanup in replication code. +@item +If one specifies @code{--code-file}, call @code{setrlmit()} to change allowed +core file size to unlimited, to be able to generate core files. +@item +Fixed bug in query cache after temporary table creation. +@item +Added @code{--count=N} (@code{-c}) to @code{mysqladmin}, to make the +program do only N iterations. To be used with @code{--sleep} (@code{-i}). +Useful in scripts. +@item +Fixed bug in multi-table @code{UPDATE}: when updating a table, +@code{do_select()} became confused about reading records from a cache. +@item +Fixed bug in multi-table @code{UPDATE} when several fields were referenced +from a single table +@item +Fixed bug in truncating nonexisting table. @item Fixed bug in @code{REVOKE} that caused user resources to be randomly set. @item @@ -50152,7 +50205,7 @@ Fixed bug in query cache initialisation with very small query cache size. @item Allow @code{DEFAULT} with @code{INSERT} statement. @item -The startup parameters @code{myisam_max_extra_sort_file_size} and +The startup parameters @code{myisam_max_sort_file_size} and @code{myisam_max_extra_sort_file_size} are now given in bytes, not megabytes. @item External system locking of MyISAM/ISAM files is now turned off by default. @@ -50168,6 +50221,8 @@ Fixed a timing bug in @code{DROP DATABASE} New @code{SET [GLOBAL | SESSION]} syntax to change thread specific and global server variables at runtime. @item +Added variable @code{slave_compressed_protocol}. +@item Renamed variable @code{query_cache_startup_type} to @code{query_cache_type}, @code{myisam_bulk_insert_tree_size} to @code{bulk_insert_buffer_size}, @code{record_buffer} to @code{read_buffer_size} and @@ -50198,7 +50253,7 @@ other databases. It is synonymous with @code{LOG(X)}. @node News-4.0.2, News-4.0.1, News-4.0.3, News-4.0.x -@appendixsubsec Changes in release 4.0.2 (01 July 2002) +@appendixsubsec Changes in release 4.0.2 (01 Jul 2002) @itemize @bullet @item @@ -50654,7 +50709,7 @@ Added script @code{mysql_explain_log.sh} to distribution. @node News-3.23.x, News-3.22.x, News-4.0.x, News -@appendixsec Changes in release 3.23.x (Stable) +@appendixsec Changes in release 3.23.x (Stable) @cindex changes, version 3.23 @@ -50704,7 +50759,7 @@ not yet 100% confident in this code. * News-3.23.46:: Changes in release 3.23.46 (29 Nov 2001) * News-3.23.45:: Changes in release 3.23.45 (22 Nov 2001) * News-3.23.44:: Changes in release 3.23.44 (31 Oct 2001) -* News-3.23.43:: Changes in release 3.23.43 +* News-3.23.43:: Changes in release 3.23.43 (04 Oct 2001) * News-3.23.42:: Changes in release 3.23.42 (08 Sep 2001) * News-3.23.41:: Changes in release 3.23.41 (11 Aug 2001) * News-3.23.40:: Changes in release 3.23.40 @@ -50722,10 +50777,10 @@ not yet 100% confident in this code. * News-3.23.29:: Changes in release 3.23.29 (16 Dec 2000) * News-3.23.28:: Changes in release 3.23.28 (22 Nov 2000: Gamma) * News-3.23.27:: Changes in release 3.23.27 (24 Oct 2000) -* News-3.23.26:: Changes in release 3.23.26 -* News-3.23.25:: Changes in release 3.23.25 +* News-3.23.26:: Changes in release 3.23.26 (18 Oct 2000) +* News-3.23.25:: Changes in release 3.23.25 (29 Sep 2000) * News-3.23.24:: Changes in release 3.23.24 (08 Sep 2000) -* News-3.23.23:: Changes in release 3.23.23 +* News-3.23.23:: Changes in release 3.23.23 (01 Sep 2000) * News-3.23.22:: Changes in release 3.23.22 (31 Jul 2000) * News-3.23.21:: Changes in release 3.23.21 * News-3.23.20:: Changes in release 3.23.20 @@ -50736,30 +50791,47 @@ not yet 100% confident in this code. * News-3.23.15:: Changes in release 3.23.15 (May 2000: Beta) * News-3.23.14:: Changes in release 3.23.14 * News-3.23.13:: Changes in release 3.23.13 -* News-3.23.12:: Changes in release 3.23.12 +* News-3.23.12:: Changes in release 3.23.12 (07 Mar 2000) * News-3.23.11:: Changes in release 3.23.11 * News-3.23.10:: Changes in release 3.23.10 * News-3.23.9:: Changes in release 3.23.9 -* News-3.23.8:: Changes in release 3.23.8 -* News-3.23.7:: Changes in release 3.23.7 +* News-3.23.8:: Changes in release 3.23.8 (02 Jan 2000) +* News-3.23.7:: Changes in release 3.23.7 (10 Dec 1999) * News-3.23.6:: Changes in release 3.23.6 -* News-3.23.5:: Changes in release 3.23.5 -* News-3.23.4:: Changes in release 3.23.4 +* News-3.23.5:: Changes in release 3.23.5 (20 Oct 1999) +* News-3.23.4:: Changes in release 3.23.4 (28 Sep 1999) * News-3.23.3:: Changes in release 3.23.3 -* News-3.23.2:: Changes in release 3.23.2 +* News-3.23.2:: Changes in release 3.23.2 (09 Aug 1999) * News-3.23.1:: Changes in release 3.23.1 -* News-3.23.0:: Changes in release 3.23.0 (Sep 1999: Alpha) +* News-3.23.0:: Changes in release 3.23.0 (05 Aug 1999: Alpha) @end menu @node News-3.23.52, News-3.23.51, News-3.23.x, News-3.23.x @appendixsubsec Changes in release 3.23.52 @itemize @bullet @item +Fixed bug with creating an auto-increment value on second part of a +@code{UNIQUE()} key where first part could contain NULL values. +@item +Don't write slave-timeout reconnects to the error log. +@item +Fixed bug with slave net read timeouting +@item +Fixed bug in ALTERing TABLE of BDB type. +@item +Fixed bug when logging @code{LOAD DATA INFILE} to binary log with no +active database. +@item +Fixed a bug in range optimiser (causing crashes). +@item Fixed possible problem in replication when doing @code{DROP DATABASE} on a database with @code{InnoDB} tables. @item -Fixed @code{mysql_info()} to return 0 for the 'Duplicates' value for -@code{INSERT DELAYED IGNORE} statements. +Fixed that @code{mysql_info()} returns 0 for 'Duplicates' when using +@code{INSERT DELAYED IGNORE}. +@item +Added @code{-DHAVE_BROKEN_REALPATH} to the Mac OS X (darwin) compile +options in @file{configure.in} to fix a failure under high load. @end itemize @node News-3.23.51, News-3.23.50, News-3.23.52, News-3.23.x @@ -51156,7 +51228,7 @@ Fixed a bug in purge which could cause crashes. @end itemize @node News-3.23.43, News-3.23.42, News-3.23.44, News-3.23.x -@appendixsubsec Changes in release 3.23.43 +@appendixsubsec Changes in release 3.23.43 (04 Oct 2001) @itemize @bullet @item @@ -52177,7 +52249,7 @@ Small portability fixes. @node News-3.23.26, News-3.23.25, News-3.23.27, News-3.23.x -@appendixsubsec Changes in release 3.23.26 +@appendixsubsec Changes in release 3.23.26 (18 Oct 2000) @itemize @bullet @item @@ -52256,7 +52328,7 @@ on a patch from John Jones. @node News-3.23.25, News-3.23.24, News-3.23.26, News-3.23.x -@appendixsubsec Changes in release 3.23.25 +@appendixsubsec Changes in release 3.23.25 (29 Sep 2000) @itemize @bullet @item @@ -52372,7 +52444,7 @@ Restored the @code{win1251} character set (it's now only marked deprecated). @node News-3.23.23, News-3.23.22, News-3.23.24, News-3.23.x -@appendixsubsec Changes in release 3.23.23 +@appendixsubsec Changes in release 3.23.23 (01 Sep 2000) @itemize @bullet @item @@ -52895,7 +52967,7 @@ Added @code{print_defaults} program to the @file{.rpm} files. Removed @node News-3.23.12, News-3.23.11, News-3.23.13, News-3.23.x -@appendixsubsec Changes in release 3.23.12 +@appendixsubsec Changes in release 3.23.12 (07 Mar 2000) @itemize @bullet @item @@ -53068,7 +53140,7 @@ Fixed problem with 8-bit characters as separators in @code{LOAD DATA INFILE}. @node News-3.23.8, News-3.23.7, News-3.23.9, News-3.23.x -@appendixsubsec Changes in release 3.23.8 +@appendixsubsec Changes in release 3.23.8 (02 Jan 2000) @itemize @bullet @item @@ -53108,7 +53180,7 @@ was too big. @node News-3.23.7, News-3.23.6, News-3.23.8, News-3.23.x -@appendixsubsec Changes in release 3.23.7 +@appendixsubsec Changes in release 3.23.7 (10 Dec 1999) @itemize @bullet @item @@ -53221,7 +53293,7 @@ Added function @code{ORD(string)}. @node News-3.23.5, News-3.23.4, News-3.23.6, News-3.23.x -@appendixsubsec Changes in release 3.23.5 +@appendixsubsec Changes in release 3.23.5 (20 Oct 1999) @itemize @bullet @item @@ -53283,7 +53355,7 @@ Fixed problem with @code{UDF} functions. @node News-3.23.4, News-3.23.3, News-3.23.5, News-3.23.x -@appendixsubsec Changes in release 3.23.4 +@appendixsubsec Changes in release 3.23.4 (28 Sep 1999) @itemize @bullet @item @@ -53362,7 +53434,7 @@ New function @code{COALESCE()}. @node News-3.23.2, News-3.23.1, News-3.23.3, News-3.23.x -@appendixsubsec Changes in release 3.23.2 +@appendixsubsec Changes in release 3.23.2 (09 Aug 1999) @itemize @bullet @item @@ -53438,7 +53510,7 @@ Fixed some compilation problems. @node News-3.23.0, , News-3.23.1, News-3.23.x -@appendixsubsec Changes in release 3.23.0 (Sep 1999: Alpha) +@appendixsubsec Changes in release 3.23.0 (05 Aug 1999: Alpha) @itemize @bullet @item @@ -53560,7 +53632,7 @@ All C client API macros are now functions to make shared libraries more reliable. Because of this, you can no longer call @code{mysql_num_fields()} on a @code{MYSQL} object, you must use @code{mysql_field_count()} instead. @item -Added use of @code{LIBEWRAP}; patch by Henning P. Schmiedehausen. +Added use of @code{LIBWRAP}; patch by Henning P. Schmiedehausen. @item Don't allow @code{AUTO_INCREMENT} for other than numerical columns. @item @@ -53600,19 +53672,19 @@ be very easy and painless. @xref{Upgrading-from-3.21}. * News-3.22.35:: Changes in release 3.22.35 * News-3.22.34:: Changes in release 3.22.34 * News-3.22.33:: Changes in release 3.22.33 -* News-3.22.32:: Changes in release 3.22.32 +* News-3.22.32:: Changes in release 3.22.32 (14 Feb 2000) * News-3.22.31:: Changes in release 3.22.31 * News-3.22.30:: Changes in release 3.22.30 -* News-3.22.29:: Changes in release 3.22.29 -* News-3.22.28:: Changes in release 3.22.28 +* News-3.22.29:: Changes in release 3.22.29 (02 Jan 2000) +* News-3.22.28:: Changes in release 3.22.28 (20 Oct 1999) * News-3.22.27:: Changes in release 3.22.27 -* News-3.22.26:: Changes in release 3.22.26 +* News-3.22.26:: Changes in release 3.22.26 (16 Sep 1999) * News-3.22.25:: Changes in release 3.22.25 -* News-3.22.24:: Changes in release 3.22.24 -* News-3.22.23:: Changes in release 3.22.23 -* News-3.22.22:: Changes in release 3.22.22 +* News-3.22.24:: Changes in release 3.22.24 (05 Jul 1999) +* News-3.22.23:: Changes in release 3.22.23 (08 Jun 1999) +* News-3.22.22:: Changes in release 3.22.22 (30 Apr 1999) * News-3.22.21:: Changes in release 3.22.21 -* News-3.22.20:: Changes in release 3.22.20 +* News-3.22.20:: Changes in release 3.22.20 (18 Mar 1999) * News-3.22.19:: Changes in release 3.22.19 (Mar 1999: Stable) * News-3.22.18:: Changes in release 3.22.18 * News-3.22.17:: Changes in release 3.22.17 @@ -53677,7 +53749,7 @@ Quicker kill of @code{SELECT DISTINCT} queries. @node News-3.22.32, News-3.22.31, News-3.22.33, News-3.22.x -@appendixsubsec Changes in release 3.22.32 +@appendixsubsec Changes in release 3.22.32 (14 Feb 2000) @itemize @bullet @item @@ -53727,7 +53799,7 @@ Fixed non-critical Y2K problem when writing short date to log files. @node News-3.22.29, News-3.22.28, News-3.22.30, News-3.22.x -@appendixsubsec Changes in release 3.22.29 +@appendixsubsec Changes in release 3.22.29 (02 Jan 2000) @itemize @bullet @item @@ -53756,7 +53828,7 @@ Fixed that @code{INSERT DELAYED} doesn't update timestamps that are given. @node News-3.22.28, News-3.22.27, News-3.22.29, News-3.22.x -@appendixsubsec Changes in release 3.22.28 +@appendixsubsec Changes in release 3.22.28 (20 Oct 1999) @itemize @bullet @item @@ -53785,7 +53857,7 @@ Fixed problem when sorting on big @code{BLOB} columns. @node News-3.22.26, News-3.22.25, News-3.22.27, News-3.22.x -@appendixsubsec Changes in release 3.22.26 +@appendixsubsec Changes in release 3.22.26 (16 Sep 1999) @itemize @bullet @item @@ -53824,7 +53896,7 @@ Fixed some small problems with the installation. @node News-3.22.24, News-3.22.23, News-3.22.25, News-3.22.x -@appendixsubsec Changes in release 3.22.24 +@appendixsubsec Changes in release 3.22.24 (05 Jul 1999) @itemize @bullet @item @@ -53844,7 +53916,7 @@ crashes some RedHat 6.0 systems @node News-3.22.23, News-3.22.22, News-3.22.24, News-3.22.x -@appendixsubsec Changes in release 3.22.23 +@appendixsubsec Changes in release 3.22.23 (08 Jun 1999) @itemize @bullet @item @@ -53872,7 +53944,7 @@ Fixed bug in @code{NATURAL LEFT JOIN}. @node News-3.22.22, News-3.22.21, News-3.22.23, News-3.22.x -@appendixsubsec Changes in release 3.22.22 +@appendixsubsec Changes in release 3.22.22 (30 Apr 1999) @itemize @bullet @item @@ -53923,7 +53995,7 @@ connections). @node News-3.22.20, News-3.22.19, News-3.22.21, News-3.22.x -@appendixsubsec Changes in release 3.22.20 +@appendixsubsec Changes in release 3.22.20 (18 Mar 1999) @itemize @bullet @item |