this is exactly what i am asking , when u say "new gamma development release" (use this for new development) what does it all mean , is it stable for production use ? i would like to know to convince work to start using it ?
-----Original Message----- From: Lenz Grimmer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 05, 2003 7:31 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: MySQL 4.0.10 is released -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, MySQL 4.0.10, 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. This is a new gamma development release, adding new features and fixing recently discovered bugs. Functionality added or changed: * Added option `--log-error[=file_name]' to `mysqld_safe' and `mysqld'. This option will force all error messages to be put in a log file if the option `--console' is not given. On Windows `--log-error' is enabled as default. * Changed some things from `Warning:' to `Note:' in the log files. * The mysqld server should now compile on Netware. * Added optimisation that if one does `GROUP BY ... ORDER BY NULL' then result is not sorted. * New command-line option for `mysqld' to replace/disable built-in stopword list, that is used in fulltext search. *Note `ft_stopword_file': SHOW VARIABLES. * Changed default stack size from 64K to 192K; This fixes a core dump problem on RedHat 8.0 and other systems with a glibc that requires > 128K stack for `gethostbyaddr()' to resolve a hostname. You can fix this for earlier MySQL versions by starting mysqld with `--thread-stack=192K'. * Added `mysql_waitpid' to the binary distribution and the `MySQL-client' RPM subpackage (required for `mysql-test-run'). * Renamed the main `MySQL' RPM package to `MySQL-server'. When updating from an older version, `MySQL-server.rpm' will simply replace `MySQL.rpm'. * If a slave is configured with `replicate_wild_do_table=db.%' or `replicate_wild_ignore_table=db.%', these rules will be applied to `CREATE/DROP DATABASE' too. * Added timeout value for `MASTER_POS_WAIT()'. Bugs fixed: * Fixed initialization of the random seed for newly created threads to give a better `rand()' distribution from the first call. * Fixed a bug that caused `mysqld' to hang when a table was opened with the `HANDLER' command and then dropped without being closed. * Fixed bug in logging to binary log (which affects replication) a query that inserts a `NULL' in an `auto_increment' field and also uses `LAST_INSERT_ID()'. * Fixed an unlikely bug that could cause a memory overrun when using `ORDER BY constant_expression'. * Fixed a table corruption in `myisamchk''s parallel repair mode. * Fixed bug in query cache invalidation on simple table renaming. * Fixed bug in `mysqladmin --relative'. * On some 64 bit systems, `show status' reported a strange number for `Open_files' and `Open_streams'. * Fixed wrong number of columns in `EXPLAIN' on empty table. * Fixed bug in `LEFT JOIN' that caused zero rows to be returned in the case the `WHERE' condition was evaluated as `FALSE' after reading const tables. (Unlikely condition). * `FLUSH PRIVILEGES' didn't correctly flush table/column privileges when `mysql.tables_priv' is empty. * Fixed bug in replication when using `LOAD DATA INFILE' one a file that updated and auto_increment field with `NULL' or `0'. This bug only affected MySQL 4.0 masters (not slaves or MySQL 3.23 masters). *NOTE*: If you have a slave that has replicated a file with generated auto_increment fields then the slave data is corrupted and you should reinitialise the affected tables from the master. * Fixed possible memory overrun when sending a blob > 16M to the client. * Fixed wrong error message when setting a `NOT NULL' field to an expression that returned `NULL'. * Fixed core dump bug in `str LIKE "%other_str%"' where `str' or `other_str' contained characters >= 128. * Fixed bug: When executing on master `LOAD DATA' and InnoDB failed with `table full' error the binary log was corrupted. Additional notes: Beginning with this release, we will cryptographically sign all MySQL distribution packages using GNU Privacy Guard (GPG, http://www.gnupg.org). For each binary distribution, there will be a file named <distribution>.asc, which includes the GPG signature for this file. The Linux RPMs include a built-in signature. To verify these signatures you need to obtain the GPG public key for "[EMAIL PROTECTED]", which you can get from the OpenPGP Public Key Server at http://www.keyserver.net or directly from this message below. You then have to import it into your GPG public keyring (see the GPG documentation for more info on how to accomplish this). Some info about the key: pub 1024D/5072E1F5 2003-02-03 MySQL Package signing key (www.mysql.com) <[EMAIL PROTECTED]> Key fingerprint = A4A9 4068 76FC BD3C 4567 70C8 8C71 8D3B 5072 E1F5 sub 2048g/6D9876B8 2003-02-03 [expires: 2008-02-02] After downloading the package and the signature file, you need to run the following command: "gpg --verify <filename>.asc". The RPM packages have a built-in signature, that you can verify with "rpm --checksig <filename.rpm>" Bye, LenZ Below is the public GPG build key: - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.0 (GNU/Linux) mQGiBD4+owwRBAC14GIfUfCyEDSIePvEW3SAFUdJBtoQHH/nJKZyQT7h9bPlUWC3 RODjQReyCITRrdwyrKUGku2FmeVGwn2u2WmDMNABLnpprWPkBdCk96+OmSLN9brZ fw2vOUgCmYv2hW0hyDHuvYlQA/BThQoADgj8AW6/0Lo7V1W9/8VuHP0gQwCgvzV3 BqOxRznNCRCRxAuAuVztHRcEAJooQK1+iSiunZMYD1WufeXfshc57S/+yeJkegNW hxwR9pRWVArNYJdDRT+rf2RUe3vpquKNQU/hnEIUHJRQqYHo8gTxvxXNQc7fJYLV K2HtkrPbP72vwsEKMYhhr0eKCbtLGfls9krjJ6sBgACyP/Vb7hiPwxh6rDZ7ITnE kYpXBACmWpP8NJTkamEnPCia2ZoOHODANwpUkP43I7jsDmgtobZX9qnrAXw+uNDI QJEXM6FSbi0LLtZciNlYsafwAPEOMDKpMqAK6IyisNtPvaLd8lH0bPAnWqcyefep rv0sxxqUEMcM3o7wwgfN83POkDasDbs3pjwPhxvhz6//62zQJ7Q7TXlTUUwgUGFj a2FnZSBzaWduaW5nIGtleSAod3d3Lm15c3FsLmNvbSkgPGJ1aWxkQG15c3FsLmNv bT6IXQQTEQIAHQUCPj6jDAUJCWYBgAULBwoDBAMVAwIDFgIBAheAAAoJEIxxjTtQ cuH1cY4AnilUwTXn8MatQOiG0a/bPxrvK/gCAJ4oinSNZRYTnblChwFaazt7PF3q zIhMBBMRAgAMBQI+PqPRBYMJZgC7AAoJEElQ4SqycpHyJOEAn1mxHijft00bKXvu cSo/pECUmppiAJ41M9MRVj5VcdH/KN/KjRtW6tHFPbkCDQQ+PqMdEAgA7+GJfxbM dY4wslPnjH9rF4N2qfWsEN/lxaZoJYc3a6M02WCnHl6ahT2/tBK2w1QI4YFteR47 gCvtgb6O1JHffOo2HfLmRDRiRjd1DTCHqeyX7CHhcghj/dNRlW2Z0l5QFEcmV9U0 Vhp3aFfWC4Ujfs3LU+hkAWzE7zaD5cH9J7yv/6xuZVw411x0h4UqsTcWMu0iM1Bz ELqX1DY7LwoPEb/O9Rkbf4fmLe11EzIaCa4PqARXQZc4dhSinMt6K3X4BrRsKTfo zBu74F47D8Ilbf5vSYHbuE5p/1oIDznkg/p8kW+3FxuWrycciqFTcNz215yyX39L XFnlLzKUb/F5GwADBQf+Lwqqa8CGrRfsOAJxim63CHfty5mUc5rUSnTslGYEIOCR 1BeQauyPZbPDsDD9MZ1ZaSafanFvwFG6Llx9xkU7tzq+vKLoWkm4u5xf3vn55Vjn Sd1aQ9eQnUcXiL4cnBGoTbOWI39EcyzgslzBdC++MPjcQTcA7p6JUVsP6oAB3FQW g54tuUo0Ec8bsM8b3Ev42LmuQT5NdKHGwHsXTPtl0klk4bQk4OajHsiy1BMahpT2 7jWjJlMiJc+IWJ0mghkKHt926s/ymfdf5HkdQ1cyvsz5tryVI3Fx78XeSYfQvuuw qp2H139pXGEkg0n6KdUOetdZWhe70YGNPw1yjWJT1IhMBBgRAgAMBQI+PqMdBQkJ ZgGAAAoJEIxxjTtQcuH17p4An3r1QpVC9yhnW2cSAjq+kr72GX0eAJ4295kl6NxY EuFApmr1+0uUq/SlsQ== =Mh4a - -----END PGP PUBLIC KEY BLOCK----- - -- For technical support contracts, visit https://order.mysql.com/?ref=mlgr __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Lenz Grimmer <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Production Engineer /_/ /_/\_, /___/\___\_\___/ Hamburg, Germany <___/ www.mysql.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+QMvKSVDhKrJykfIRApLCAJwM+vs6+tGYjaI0/UAKjK0R6PXHDgCeOdZQ 5tWDfkRyYniij3bKPSCOIaU= =f7Oj -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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
