Updated the description on version 3.23, and added

--enable-thread-safe-client item to Change log.
parent 815bd107
...@@ -754,8 +754,8 @@ MySQL internals ...@@ -754,8 +754,8 @@ MySQL internals
MySQL change history MySQL change history
* News-3.23.x:: Changes in release 3.23.x (Released as beta) * News-3.23.x:: Changes in release 3.23.x (Recommended; beta)
* News-3.22.x:: Changes in release 3.22.x (Recommended version) * News-3.22.x:: Changes in release 3.22.x (Still supported)
* News-3.21.x:: Changes in release 3.21.x * News-3.21.x:: Changes in release 3.21.x
* News-3.20.x:: Changes in release 3.20.x * News-3.20.x:: Changes in release 3.20.x
* News-3.19.x:: Changes in release 3.19.x * News-3.19.x:: Changes in release 3.19.x
...@@ -35344,30 +35344,28 @@ find on the ...@@ -35344,30 +35344,28 @@ find on the
this means that the version has not yet been released! this means that the version has not yet been released!
@menu @menu
* News-3.23.x:: Changes in release 3.23.x (Released as beta) * News-3.23.x:: Changes in release 3.23.x (Recommended; beta)
* News-3.22.x:: Changes in release 3.22.x (Recommended version) * News-3.22.x:: Changes in release 3.22.x (Still supported)
* News-3.21.x:: Changes in release 3.21.x * News-3.21.x:: Changes in release 3.21.x
* News-3.20.x:: Changes in release 3.20.x * News-3.20.x:: Changes in release 3.20.x
* News-3.19.x:: Changes in release 3.19.x * News-3.19.x:: Changes in release 3.19.x
@end menu @end menu
@node News-3.23.x, News-3.22.x, News, News @node News-3.23.x, News-3.22.x, News, News
@appendixsec Changes in release 3.23.x (Released as beta) @appendixsec Changes in release 3.23.x (Recommended; beta)
The major difference between release 3.23 and releases 3.22 and 3.21 is that The 3.23 release has several major new features that are not
3.23 contains a new ISAM library (MyISAM), which is more tuned for SQL present in the 3.22 or 3.21 releases. We have added two new
than the old ISAM was. table types: MyISAM, a new ISAM library which is tuned for SQL
and supports large files; and BerkeleyDB which uses the Berkeley
The 3.23 release is under development, and things will be added at a DB library from Sleepycat Software to implement transaction-safe
fast pace to it. For the moment we recommend this version only for tables. The 3.23 release also includes support for database
users that desperately need a new feature that is found only in this replication between a master and many slaves.
release (like big file support and machine-independent tables). (Note
that all new functionality in @strong{MySQL} 3.23 is extensively tested, but as
this release involves much new code, it's difficult to test everything).
We are not adding any more new features that are likely to break any We are not adding any more new features that are likely to break any
old code in @strong{MySQL} 3.23 so this version should stabilise pretty soon old code in @strong{MySQL} 3.23, so we recommend that you use this
and will soon be declared beta, gamma and release. version. The replication and BerkeleyDB code is still under development,
though, so 3.23 is not relesed as a stable version yet.
@menu @menu
* News-3.23.23:: Changes in release 3.23.23 * News-3.23.23:: Changes in release 3.23.23
...@@ -35400,6 +35398,12 @@ and will soon be declared beta, gamma and release. ...@@ -35400,6 +35398,12 @@ and will soon be declared beta, gamma and release.
@appendixsubsec Changes in release 3.23.23 @appendixsubsec Changes in release 3.23.23
@itemize @bullet @itemize @bullet
@item @item
Changed behavior of @code{--enable-thread-safe-client} so
that both non-threaded (@code{-lmysqlclient}) and threaded
(@code{-lmysqlclient_r}) libraries are built. Users who linked
against a threaded @code{-lmysqlclient} will need to link against
@code{libmysqlclient_r} now.
@item
Added atomic @code{RENAME} command. Added atomic @code{RENAME} command.
@item @item
Don't count entries with @code{NULL} in @code{COUNT(DISTINCT ..)}. Don't count entries with @code{NULL} in @code{COUNT(DISTINCT ..)}.
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