List:General Discussion« Previous MessageNext Message »
From:Dan Pelton Date:September 12 2000 12:23pm
Subject:Re: MySQL 3.23.24 released
View as plain text  
Is MySQL 3.22 the latest production release?

Michael Widenius wrote:
> 
> Hi!
> 
> MySQL 3.23.24 is now released
> 
> This was an unscheduled release to restore the character for latin1 as
> it was before 3.23.23.
> 
> Users that are using 3.23.23 should upgrade to this version!  If you
> are are using 3.23.23 and have keys on CHAR, VARCHAR or BLOB columns
> that may contain characters > 128 (like Scandinavia characters), you
> should run a CHECK on all tables and REPAIR any tables for which you
> get an warning!
> 
> After 3.23.24 was released, but before this announcement, we noticed a
> problem with mysqldump from 3.23.23 where some char columns where not properly
> escaped.  We fill shortly make a new binary release that fixes this.
> You can patch the 3.23.24 source with the following to fix this:
> 
> --------
> 
> (/my/mysql) bk diffs include/mysql.h
> ===== include/mysql.h 1.19 vs edited =====
> 77c77
> < #define INTERNAL_NUM_FIELD(f) (((f)->type <= FIELD_TYPE_INT24 &&
> (f)->type !=
> FIELD_TYPE_TIMESTAMP || (f)->length == 14 || (f)->length == 8) || (f)->type
> == F
> IELD_TYPE_YEAR)
> ---
> > #define INTERNAL_NUM_FIELD(f) (((f)->type <= FIELD_TYPE_INT24 &&
> ((f)->type !=
>  FIELD_TYPE_TIMESTAMP || (f)->length == 14 || (f)->length == 8)) ||
> (f)->type ==
>  FIELD_TYPE_YEAR)
> ------------
> 
> You can of course also use any old version of the mysqldump program to
> avoid the above problem!
> 
> Sorry for the confusion :(  We are REALLY trying to stabilize 3.23 as
> soon as possible;  It still hope that 3.23.25 will be a gamma version...
> 
> Changes in release 3.23.24
> --------------------------
> 
>    * Added mysqld variable `created_tmp_disk_tables'.
> 
>    * To make it possibly to reliable dump and restore tables with
>      `TIMESTAMP(X)' columns, `MySQL' now reports columns with X other
>      than 14 or 8 to be strings.
> 
>    * Changed sort order for latin1 as it was before 3.23.22.  Any table
>      with `CHAR' columns that may have characters > ASCII 128 created or
>      modified with 3.23.22 must be repaired!
> 
>    * Fixed small memory leak introduced from 3.23.22 when creating a
>      temporary table.
> 
>    * Fixed problem with BDB tables and reading on unique (not primary)
>      key.
> 
>    * Restored the win1251 character set (it's now only marked
>      deprecated).
> 
> Regards,
> Monty
> 
> --
> ---------------------------------------------------------------------
> Please check "http://www.mysql.com/php/manual.php" before
> posting. To request this thread, e-mail mysql-thread50281@stripped
> 
> To unsubscribe, send a message to:
>     <mysql-unsubscribe-dnp=ams.org@stripped>
> 
> If you have a broken mail client that cannot send a message to the above
> address(Microsoft Outlook), you can use http://lists.mysql.com/php/unsubscribe.php


Dan Pelton
Thread
Inserting id's into AUTO_INCREMENT tablesMorten12 Mar
  • Re: Inserting id's into AUTO_INCREMENT tablesThimble Smith12 Mar
  • Re: Inserting id's into AUTO_INCREMENT tablesChristian Mack12 Mar
  • Re: Inserting id's into AUTO_INCREMENT tablesEd Carp12 Mar
  • Re: MySQL 3.23.24 releasedJerome Abela11 Sep
    • Re: MySQL 3.23.24 releasedMichael Widenius11 Sep
  • Re: MySQL 3.23.24 releasedDan Pelton12 Sep
Re: MySQL 3.23.24 releasedRichard Ellerbrock12 Sep
  • RE: MySQL 3.23.24 releasedSander Pilon12 Sep