|
|
Subscribe / Log in / New account

MySQL 4.1.0 released

From:  Lenz Grimmer <lenz@mysql.com>
To:  MySQL Announcement list <announce@lists.mysql.com>
Subject:  MySQL 4.1.0 has been released
Date:  Wed, 9 Apr 2003 21:43:51 +0200 (CEST)
Cc:  mysql@lists.mysql.com, packagers@lists.mysql.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

MySQL 4.1.0, 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 in time -
if you can't find this version on some mirror, please try again later or
choose another download site.

This is the first Alpha development release of the 4.1 tree, adding many
new features (see below). As this code is currently labelled "Alpha", we
do not recommend that this version be used in production environments yet!

However, we encourage you to test and evaluate it and, more importantly,
report any bugs or observations to our bug tracking database at
http://bugs.mysql.com. Please note, that for us to resolve a bug report, a
reproducible test is required. See "How to report a bug" at
http://bugs.mysql.com/how-to-report.php for more details before filing a bug
report. We appreciate your support!

Some new features include:

 * Subqueries:
        SELECT * FROM t1 WHERE t1.a=(SELECT t2.b FROM t2);

        SELECT * FROM t1 WHERE (1,2,3) IN (SELECT a,b,c FROM t2);

 * Derived tables:
        SELECT t1.a FROM t1, (SELECT * FROM t2) t3 WHERE t1.a=t3.a;

 * `INSERT ... ON DUPLICATE KEY UPDATE ...' syntax.  This allows you
   to `UPDATE' an existing row if the insert would cause a duplicate
   value in a `PRIMARY' or `UNIQUE' key. (`REPLACE' allows you to
   overwrite an existing row, which is something entirely different.)
   (See http://www.mysql.com/doc/en/INSERT.html for more info)

 * A newly designed `GROUP_CONCAT()' aggregate function.
   (See http://www.mysql.com/doc/en/Group_by_functions.html for more info)

 * Extensive Unicode (UTF8) support.

 * Character sets can be defined per column, table and database.

 * `BTREE' index on `HEAP' tables.

 * Support for OpenGIS (Geographical data).
   (See http://www.mysql.com/doc/en/GIS_spatial_extensions_in_MySQL.html
   for more info)

 * `SHOW WARNINGS' shows warnings for the last command.
   (See http://www.mysql.com/doc/en/SHOW_WARNINGS.html for more info)

 * Faster binary protocol with prepared statements and parameter
   binding.
   (See http://www.mysql.com/doc/en/C_API_Prepared_statements.html for
   more info)

 * Multi-line queries: You can now issue several queries at once and
   then read the results in one go.  *Note C API multiple queries::.
   (See http://www.mysql.com/doc/en/C_API_multiple_queries.html for more
   info)

 * Create Table: `CREATE [TEMPORARY] TABLE [IF NOT EXISTS] table LIKE
   table'.

 * Server based `HELP command' that can be used in the `mysql'
   command line client (and other clients) to get help for SQL
   commands.

For a more detailed list of changes in MySQL 4.1.0, please also see
http://www.mysql.com/doc/en/News-4.1.0.html and
http://www.mysql.com/doc/en/MySQL_4.1_In_A_Nutshell.html

Bye,
	LenZ
- -- 
For technical support contracts, visit https://order.mysql.com/?ref=mlgr
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /      Mr. Lenz Grimmer <lenz@mysql.com>
 / /|_/ / // /\ \/ /_/ / /__     MySQL AB, Production Engineer
/_/  /_/\_, /___/\___\_\___/     Hamburg, Germany
       <___/   www.mysql.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE+lHf5SVDhKrJykfIRApiGAJ97E/+HOtg8NtknyX9YAh+TiyCi8QCfRIBF
aNHIFg5ZfyYuinpEcjBko9U=
=Lakx
-----END PGP SIGNATURE-----



to post comments

MySQL 4.1.0 released

Posted Apr 10, 2003 9:31 UTC (Thu) by Dom2 (guest, #458) [Link]

Hmmm, I'm curious as to how a join would work on two columns of different character sets....

-Dom

MySQL 4.1.0 released

Posted Apr 10, 2003 15:32 UTC (Thu) by Baylink (guest, #755) [Link] (1 responses)

It's version number is 4.1.0... but it's an *ALPHA*.

<screech volume=loud type=anguished>

"Just keep repeating it until they follow along" seems to be working for Bush... could we start calling this 4.1alpha1, like real software engineers, and hope that it might stick?

MySQL have very good versioning

Posted Apr 10, 2003 18:37 UTC (Thu) by coriordan (guest, #7544) [Link]

Actually, MySQL's version scheme is very good.

> could we start calling this 4.1alpha1

No, that's not what the "alpha" means. "alpha" refers to how tested the
new parts of the code are. In a month or two, when all major bugs
have been squashed, a version (maybe 4.1.4) will be judged as "beta"
quality. Once bug reports stop coming in for 4.1.X they will announce
that it is "Production" quality (this could be 4.1.20 or 4.1.15 or whatever)

The Apache Foundation run a similar scheme. The actual version number of
"Apache 2.0" was 2.0.24.

It's a bit like calling Linux 2.5 "Alpha" and, 2.4.21 "Production".

One of it's purposes is to show the different user groups when they should
adopt the new version. Most developers probably use the Alpha or Beta
branches, while mission-critical datacenters would only use Production
branches.

Ciaran O'Riordan


Copyright © 2003, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds