database.sarang.net
UserID
Passwd
Database
DBMS
ㆍMySQL
PostgreSQL
Firebird
Oracle
Informix
Sybase
MS-SQL
DB2
Cache
CUBRID
LDAP
ALTIBASE
Tibero
DB 문서들
스터디
Community
공지사항
자유게시판
구인|구직
DSN 갤러리
도움주신분들
Admin
운영게시판
최근게시물
MySQL News 18818 게시물 읽기
 News | Q&A | Columns | Tutorials | Devel | Files | Links
No. 18818
MySQL 4.0.12 has been Released
작성자
정동철(zzori)
작성일
2003-03-19 07:31
조회수
9,834

http://mysql.new21.com

http://mysql.new21.com/downloads/mysql-4.0.html

 

오호^^ 기뿌다~~

드려 오랫동안 기다린 감마 딱지 때기~~

4.0.12 부터는 이제 gamma 대신에... production 아 머쪄 +_+ ㅋㅋ

4.0.12 로 업글해야지

 

MySQL 4.0.12, a new version of the popular Open Source Database, has been

released. It is now available in source and binary form for a number of

platforms from our download pages at http://www.mysql.com/downloads/ and

mirror sites.

 

Note that not all mirror sites may be up to date at this point of time -

if you can't find this version on some mirror, please try again later or

choose another download site.

 

Starting with MySQL 4.0.12, MySQL 4.0 is now labelled as "production"

instead of "gamma".

 

Users of MySQL 3.23 are encouraged to upgrade, since MySQL 3.23 will now

be phased out slowly. It will still be supported, but only critical bug

and security fixes will be applied to the 3.23 code base.

 

News from the ChangeLog:

 

Functionality added or changed:

 

* `mysqld' no longer reads options from world-writeable config files.

 

* Integer values between 9223372036854775807 and 9999999999999999999

are now regarded as unsigned longlongs, not as floats. This makes

these values work similar to values between 10000000000000000000

and 18446744073709551615.

 

* `SHOW PROCESSLIST' will now include the client TCP port after the

hostname to make it easier to know from which client the request

originated.

 

Bugs fixed:

 

* Fixed `mysqld' crash on extremely small values of `sort_buffer'

variable.

 

* `INSERT INTO u SELECT ... FROM t' was written too late to the

binary log if t was very frequently updated during the execution of

this query. This could cause a problem with `mysqlbinlog' or

replication. The master must be upgraded, not the slave. (bug #136).

 

* Fixed checking of random part of `WHERE' clause (bug #142).

 

* Fixed a bug with `multi-table updates' with `InnoDB' tables. This

bug occured as, in many cases, `InnoDB' tables can not be updated

"on the fly", but offsets to the records have to be stored in a

temporary table.

 

* Added missing file `mysql_secure_installation' to the `server' RPM

subpackage (bug #141).

 

* Fixed MySQL (and `myisamchk') crash on artificially corrupted

`.MYI' files.

 

* Don't allow `BACKUP TABLE' to overwrite existing files.

 

* Fixed a bug with multi-table `UPDATE's when user had all privileges

on the database where tables are located and there were any

entries in `tables_priv' table, i.e. `grant_option' was true.

 

* Fixed a bug that allowed a user with table or column grants on

some table, `TRUNCATE' any table in the same database.

 

* Fixed deadlock when doing `LOCK TABLE' followed by `DROP TABLE' in

the same thread. In this case one could still kill the thread

with `KILL'.

 

* `LOAD DATA LOCAL INFILE' was not properly written to the binary

log (hence not properly replicated). (bug #82).

 

* `RAND()' entries were not read correctly by `mysqlbinlog' from the

binary log which caused problems when restoring a table that was

inserted with `RAND()'. `INSERT INTO t1 VALUES(RAND())'. In

replication this worked ok.

 

* `SET SQL_LOG_BIN=0' was ignored for `INSERT DELAYED' queries.

(bug #104).

 

* `SHOW SLAVE STATUS' reported too old positions (columns

`Relay_Master_Log_File' and `Exec_master_log_pos') for the last

executed statement from the master, if this statement was the

`COMMIT' of a transaction. The master must be upgraded for that,

not the slave. (bug #52).

 

* `LOAD DATA INFILE' was not replicated by the slave if

`replicate_*_table' was set on the slave. (bug #86).

 

* After `RESET SLAVE', the coordinates displayed by `SHOW SLAVE

STATUS' looked un-reset (though they were, but only internally).

(bug #70).

 

* Fixed query cache invalidation on `LOAD DATA'.

 

* Fixed memory leak on `ANALYZE' procedure with error.

 

* Fixed a bug in handling `CHAR(0)' columns that could cause wrong

results from the query.

 

* Fixed rare bug with wrong initialization of `AUTO_INCREMENT'

column, as a secondary column in a multi-column key (*note

`AUTO_INCREMENT' on secondary column in a multi-column key:

example-AUTO_INCREMENT.), when data was inserted with `INSERT ...

SELECT' or `LOAD DATA' into an empty table.

 

* On windows, `STOP SLAVE' didn't stop the slave until the slave got

one new command from the master (this bug has been fixed for MySQL

4.0.11 by releasing updated 4.0.11a windows packages, which

include this individual fix on top of the 4.0.11 sources).

(bug #69).

 

* Fixed a crash when no database was selected and `LOAD DATA' command

was issued with full table name specified, including database

prefix.

 

* Fixed a crash when shutting down replication on some platforms

(e.g. Mac OS X).

 

* Fixed a portability bug with `pthread_attr_getstacksize' on

HP-UX 10.20 (Patch was also included in 4.0.11a sources).

 

* Fixed the `bigint' test to not fail on some platforms (e.g. HP-UX

and Tru64) due to different return values of the `atof()' function.

 

* Fixed the `rpl_rotate_logs' test to not fail on certain platforms

(e.g. Mac OS X) due to a too long file name (changed

`slave-master-info.opt' to `.slave-mi').

이 글에 대한 댓글이 총 1건 있습니다.

 

님이 2003-04-02 04:51에 작성한 댓글입니다.
[Top]
No.
제목
작성자
작성일
조회
20472MySQL release MaxDB
정재익
2003-11-21
8017
20316MySQL 4.0.16 has been released
강병기
2003-10-29
9869
20076MySQL 4.0.15 has been released
강병기
2003-09-23
8717
18818MySQL 4.0.12 has been Released [1]
정동철
2003-03-19
9834
18799MySQL/InnoDB-3.23.56 Released
정동철
2003-03-17
7761
18330MySQL 4.0.9 Released
허정수
2003-01-15
7572
18272MySQL 4.0.8 Released ! [3]
허정수
2003-01-09
8876
Valid XHTML 1.0!
All about the DATABASE... Copyleft 1999-2024 DSN, All rights reserved.
작업시간: 0.025초, 이곳 서비스는
	PostgreSQL v16.4로 자료를 관리합니다