Hi!

3.23.37 is now released.

This release mainly fixes some minor bugs, so we assume that most
users doesn't have to upgrade from 3.23.36.

The main change is that Innobase tables changed name to InnoDB to not
conflict with the German INNOBASE company.  If you are using Innobase,
you need to change all your options in your startup and config files
from innobase to innodb.  (You can still create tables with
type=INNOBASE, but this should be changed to type=INNODB over time).

We are just now building the first MySQL-Max binaries with support for
Berkeley DB and InnoDB tables.  The first one will be a Linux x86 RPM
(which should be available tomorrow), but other binaries should be
available within a few days (or when 3.23.38 is released if we
have to do any major porting change).

Because of a problem on our windows computer, the windows version of
3.23.37 will be delayed a couple of days.


Changes in release 3.23.37
--------------------------
 
   * Fixed a bug when using `HEAP' tables with `LIKE'.
 
   * Added `--mysql-version' to `safe_mysqld'
 
   * Changed `INNOBASE' to `InnoDB' (because the `INNOBASE' name was
     already used). All `configure' options and `mysqld' start options
     are now using `innodb' instead of `innobase'. This means that you
     have to change any configuration files where you have used
     `innobase' options before upgrading to this version!
 
   * Fixed bug when using indexes on `CHAR(255) NULL' columns.
 
   * Slave thread will now be started even if `master-host' is not set,
     as long as `server-id' is set and valid `master.info' is present
 
   * Partial updates ( terminated with kill) are now logged with a
     special error code to the binary log. Slave will refuse to execute
     them if the error code indicates the update was terminated
     abnormally, and will have to be recovered with `SET
     SQL_SLAVE_SKIP_COUNTER=1; SLAVE START' after a manual sanity
     check/correction of data integrity
 
   * Fixed bug that erroneously logged a drop of internal temporary
     table  on thread termination to the binary log - bug affected
     replication
 
   * Fixed a bug in `REGEXP()' on 64-bit machines.
 
   * `UPDATE' and `DELETE' with `WHERE unique_key_part IS NULL' didn't
     update/delete all rows.
 
   * Disabled `INSERT DELAYED' for tables that supports transactions.
 
   * Fixed bug when using date functions on `TEXT'/`BLOB' column with
     wrong date format.
 
   * UDF's now also works on windows. (Patch by Ralph Mason)

   * Fixed bug in `ALTER TABLE' and `LOAD DATA INFILE' that disabled
     key-sorting. These command should now be faster in most cases.
 
   * Fixed performance bug where reopened tables (tables that had been
     waiting for `FLUSH' or `REPAIR') would not use indexes for the
     next query.
 
   * Fixed problem with `ALTER TABLE' to Innobase tables on Freebsd.
 
   * Added `mysqld' variables `myisam_max_sort_file_size' and
     `myisam_max_extra_sort_file_size'.
 
   * Initialize signals early to avoid problem with signals in Innobase.
 
   * Applied patch for the `tis620' character set to make comparisons
     case-independent and to fix a bug in `LIKE' for this character set.
     *NOTE*: All tables that uses the `tis620' character set must be
     fixed with  `myisamchk -r' or `REPAIR TABLE' !
 
   * Added `--skip-safemalloc' option to `mysqld'.

Regards,
Monty

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to