Re: MySQL 4.0.5(a) is released

2002-11-30 Thread Steven Bielik 
Stefan, Lenz, et al.,
May I suggest, for backward compatibility, obsolescing the variable
(NOOP) instead of removing it.
Happy Holidays. :-)
==_-+- Steve


- Original Message -
From: Stefan Hinz, iConnect (Berlin) [EMAIL PROTECTED]
To: Lenz Grimmer [EMAIL PROTECTED]; MySQL announce list
[EMAIL PROTECTED]
Cc: MySQL mailing list [EMAIL PROTECTED]
Sent: Thursday, November 28, 2002 4:32 PM
Subject: Re: MySQL 4.0.5(a) is released


 Dear Lenz,

  Removed variable `safe_show_database' as it was not used anymore.

 What will ISPs say about this one? They use 'safe_show_database' for their
 MySQL setups, so their customers on virtual MySQL hosts cannot see other
 customers' databases. (It's more likely that you won't attack something
 which you cannot see.)

 Or am I missing out on something?

 Regards,
 --
   Stefan Hinz [EMAIL PROTECTED]
   CEO / Geschäftsleitung iConnect GmbH http://iConnect.de
   Heesestr. 6, 12169 Berlin (Germany)
   Telefon: +49 30 7970948-0  Fax: +49 30 7970948-3


 - Original Message -
 From: Lenz Grimmer [EMAIL PROTECTED]
 To: MySQL announce list [EMAIL PROTECTED]
 Cc: MySQL mailing list [EMAIL PROTECTED]
 Sent: Wednesday, November 27, 2002 10:41 PM
 Subject: MySQL 4.0.5(a) is released


 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,

 MySQL 4.0.5, a new version of the world's most 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.

 This is a new beta development release, adding new features and fixing
 recently discovered bugs. This will be the last release labelled as
beta -
 the upcoming MySQL 4.0.6 will be labelled gamma, which emphasizes the
fact
 that the MySQL 4.0 code base has further stabilized and is becoming ready
 for
 productive use.

 To avoid confusion between the product names of the GPL and non-GPL
 (commercial) binaries, MySQL AB has now further refined the new naming
 scheme. Starting with MySQL 4.0.5 and onwards, the following binaries will
 be
 available:

 MySQL Standard (GPL)
 This is the recommended binary for most users that want to use MySQL under
 the
 terms of the GNU General Public License (GPL). It includes the InnoDB
 Storage
 Engine and all default features that are considered stable and useful
enough
 for general usage.

 MySQL Max (GPL)
 This is an enhanced version of the Standard GPL package. In addition to
the
 InnoDB Storage Engine, it includes additional features like the Berkeley
DB
 (BDB) Storage Engine (certain platforms only) as well as other additional
 features that are either not exhaustively tested yet or not required for
 most
 users, e.g. OpenSSL (where available), User defined functions (UDFs), or
 BIG_TABLE support. When these features have matured and proven to be
stable
 enough, they will be part of future versions of the Standard binaries.
 Please
 note, that not all of these features are included in all binaries.

 MySQL Classic (Commercial License)
 Similar to MySQL Standard, but *without* InnoDB and only available as a
 commercial licensed version.

 MySQL Pro (Commercial License)
 Similar to MySQL Standard (*including* InnoDB), but only available as a
 commercial licensed version.


 - From the 4.0.5 ChangeLog:

 Functionality added or changed:

  * Changed handling of last argument in `WEEK()' so that one can get
week number according to the ISO 8601 specification.  (Old code
should still work).
  * Fixed that `INSERT DELAY' threads doesn't hang on `Waiting for
INSERT' when one sends a `SIGHUP' to `mysqld'.
  * Change that `AND' works according to SQL ANSI99 when it comes to
`NULL' handling. In practice, this only affects queries where you
do something like `WHERE ... NOT (NULL AND 0)'.
  * `mysqld' will now resolve `basedir' to its full path (with
`realpath()'). This enables one to use relative symlinks to the
MySQL installation directory.  This will however cause `show
variables' to report different directories on systems where there
is a symbolic link in the path.
  * Fixed that MySQL will not use an index scan on an index that has
been disabled with `IGNORE INDEX' or `USE INDEX'.
  * Added `--use-frm' option to `mysqlcheck'. When used with `REPAIR',
it gets the table structure from the `.frm' file, so the table can
be repaired even if the `.MYI' header is corrupted.
  * Fixed bug in `MAX()' optimization when used with `JOIN' and `ON'
expressions.
  * Added support for reading of MySQL 4.1 table definition files.
  * `BETWEEN' behaviour changed (*note Comparison Operators::).  Now
`datetime_col BETWEEN timestamp AND timespamp' should work as
expected.
  * One can create `TEMPORARY' `MERGE' tables now.
  * `DELETE FROM myisam_table' now shrinks not only the `.MYD' file but
also the `.MYI' file.
  * When one uses the `--open-files-limit=#' option to `mysqld_safe'
it's now passed

Re: MySQL 4.0.5(a) is released

2002-11-30 Thread Steven Bielik 
Stefan, Lenz, et al.,
May I suggest, for backward compatibility, obsolescing the
'safe_show_database' variable (a NOOP) instead of removing it?
Also, IMPO, it is better practice to grant each customer's user access to
their own database(s). Each customer's rights can then be specifically
managed by security administrators and/or automagically via script, as
apposed to relying on the database to do the job.
Happy Holidays. :-)
==_-+- Steve


- Original Message -
From: Stefan Hinz, iConnect (Berlin) [EMAIL PROTECTED]
To: Lenz Grimmer [EMAIL PROTECTED]; MySQL announce list
[EMAIL PROTECTED]
Cc: MySQL mailing list [EMAIL PROTECTED]
Sent: Thursday, November 28, 2002 4:32 PM
Subject: Re: MySQL 4.0.5(a) is released


 Dear Lenz,

  Removed variable `safe_show_database' as it was not used anymore.

 What will ISPs say about this one? They use 'safe_show_database' for their
 MySQL setups, so their customers on virtual MySQL hosts cannot see other
 customers' databases. (It's more likely that you won't attack something
 which you cannot see.)

 Or am I missing out on something?

 Regards,
 --
   Stefan Hinz [EMAIL PROTECTED]
   CEO / Geschäftsleitung iConnect GmbH http://iConnect.de
   Heesestr. 6, 12169 Berlin (Germany)
   Telefon: +49 30 7970948-0  Fax: +49 30 7970948-3


 - Original Message -
 From: Lenz Grimmer [EMAIL PROTECTED]
 To: MySQL announce list [EMAIL PROTECTED]
 Cc: MySQL mailing list [EMAIL PROTECTED]
 Sent: Wednesday, November 27, 2002 10:41 PM
 Subject: MySQL 4.0.5(a) is released


 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,

 MySQL 4.0.5, a new version of the world's most 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.

 This is a new beta development release, adding new features and fixing
 recently discovered bugs. This will be the last release labelled as
beta -
 the upcoming MySQL 4.0.6 will be labelled gamma, which emphasizes the
fact
 that the MySQL 4.0 code base has further stabilized and is becoming ready
 for
 productive use.

 To avoid confusion between the product names of the GPL and non-GPL
 (commercial) binaries, MySQL AB has now further refined the new naming
 scheme. Starting with MySQL 4.0.5 and onwards, the following binaries will
 be
 available:

 MySQL Standard (GPL)
 This is the recommended binary for most users that want to use MySQL under
 the
 terms of the GNU General Public License (GPL). It includes the InnoDB
 Storage
 Engine and all default features that are considered stable and useful
enough
 for general usage.

 MySQL Max (GPL)
 This is an enhanced version of the Standard GPL package. In addition to
the
 InnoDB Storage Engine, it includes additional features like the Berkeley
DB
 (BDB) Storage Engine (certain platforms only) as well as other additional
 features that are either not exhaustively tested yet or not required for
 most
 users, e.g. OpenSSL (where available), User defined functions (UDFs), or
 BIG_TABLE support. When these features have matured and proven to be
stable
 enough, they will be part of future versions of the Standard binaries.
 Please
 note, that not all of these features are included in all binaries.

 MySQL Classic (Commercial License)
 Similar to MySQL Standard, but *without* InnoDB and only available as a
 commercial licensed version.

 MySQL Pro (Commercial License)
 Similar to MySQL Standard (*including* InnoDB), but only available as a
 commercial licensed version.


 - From the 4.0.5 ChangeLog:

 Functionality added or changed:

  * Changed handling of last argument in `WEEK()' so that one can get
week number according to the ISO 8601 specification.  (Old code
should still work).
  * Fixed that `INSERT DELAY' threads doesn't hang on `Waiting for
INSERT' when one sends a `SIGHUP' to `mysqld'.
  * Change that `AND' works according to SQL ANSI99 when it comes to
`NULL' handling. In practice, this only affects queries where you
do something like `WHERE ... NOT (NULL AND 0)'.
  * `mysqld' will now resolve `basedir' to its full path (with
`realpath()'). This enables one to use relative symlinks to the
MySQL installation directory.  This will however cause `show
variables' to report different directories on systems where there
is a symbolic link in the path.
  * Fixed that MySQL will not use an index scan on an index that has
been disabled with `IGNORE INDEX' or `USE INDEX'.
  * Added `--use-frm' option to `mysqlcheck'. When used with `REPAIR',
it gets the table structure from the `.frm' file, so the table can
be repaired even if the `.MYI' header is corrupted.
  * Fixed bug in `MAX()' optimization when used with `JOIN' and `ON'
expressions.
  * Added support for reading of MySQL 4.1 table definition files.
  * `BETWEEN' behaviour changed (*note Comparison Operators::).  Now
`datetime_col BETWEEN timestamp

Re: MySQL 4.0.5(a) is released

2002-11-29 Thread Alexander Keremidarski 
Dear Stefan,
Stefan Hinz, iConnect (Berlin) wrote:

Dear Lenz,



Removed variable `safe_show_database' as it was not used anymore.



What will ISPs say about this one? They use 'safe_show_database' for their
MySQL setups, so their customers on virtual MySQL hosts cannot see other
customers' databases. (It's more likely that you won't attack something
which you cannot see.)

Or am I missing out on something?



Functionality is still there, but implemented at the place it belongs to.

Pay attention on Privlieges tables 4.0.5 uses. You will see there is:

`Show_db_priv` enum('N','Y') NOT NULL default 'N'

i.e. User must be granted explicitly this privilege in order to be able to use:
SHOW DATABASES;

Suggested way for setting this Ptivilege is ofcourse command:
GRANT SHOW DATABASES;

I hope you will agree that this approach provides much better flexibility and is 
more natural than mysqld starting option.

If you still have concerns, please don't hesitate to share them with us.

--
 For technical support contracts, visit https://order.mysql.com/
__  ___ ___   __
   /  |/  /_ __/ __/ __ \/ /Mr. Alexander Keremidarski [EMAIL PROTECTED]
  / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Developer
 /_/  /_/\_, /___/\___\_\___/   Sofia, Bulgaria
 ___/   www.mysql.com



-
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

Re: MySQL 4.0.5(a) is released

2002-11-29 Thread Sinisa Milivojevic 
Stefan Hinz, iConnect \(Berlin\) writes:
 Dear Lenz,
 
  Removed variable `safe_show_database' as it was not used anymore.
 
 What will ISPs say about this one? They use 'safe_show_database' for their
 MySQL setups, so their customers on virtual MySQL hosts cannot see other
 customers' databases. (It's more likely that you won't attack something
 which you cannot see.)
 
 Or am I missing out on something?
 
 Regards,
 --
   Stefan Hinz [EMAIL PROTECTED]
   CEO / Geschäftsleitung iConnect GmbH http://iConnect.de
   Heesestr. 6, 12169 Berlin (Germany)
   Telefon: +49 30 7970948-0  Fax: +49 30 7970948-3
 

Hi!

Variable has been removed but the option --safe-show-database remain.

-- 
Regards,
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED]
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Fulltime Developer
/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
   ___/   www.mysql.com


-
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

Re: MySQL 4.0.5(a) is released

2002-11-29 Thread Listen Hinz 
Dear Lenz,

 `Show_db_priv` enum('N','Y') NOT NULL default 'N'
 i.e. User must be granted explicitly this privilege in order to be
able to use:
 SHOW DATABASES;
 Suggested way for setting this Ptivilege is ofcourse command:
 GRANT SHOW DATABASES;

Sound it bit strange in a GRANT select, show databases, update context
as it has two words, in opposite to all other privileges that have only
one word.

 I hope you will agree that this approach provides much better
flexibility and
 is more natural than mysqld starting option.

Totally agree :)

Regards,
--
  Stefan Hinz [EMAIL PROTECTED]
  Geschäftsführer / CEO iConnect GmbH http://iConnect.de
  Heesestr. 6, 12169 Berlin (Germany)
  Tel: +49 30 7970948-0  Fax: +49 30 7970948-3


- Original Message -
From: Alexander Keremidarski [EMAIL PROTECTED]
To: Stefan Hinz, iConnect (Berlin) [EMAIL PROTECTED]
Cc: Lenz Grimmer [EMAIL PROTECTED]; MySQL announce list
[EMAIL PROTECTED]; MySQL mailing list [EMAIL PROTECTED]
Sent: Friday, November 29, 2002 11:15 AM
Subject: Re: MySQL 4.0.5(a) is released


 Dear Stefan,
 Stefan Hinz, iConnect (Berlin) wrote:
  Dear Lenz,
 
 
 Removed variable `safe_show_database' as it was not used anymore.
 
 
  What will ISPs say about this one? They use 'safe_show_database' for
their
  MySQL setups, so their customers on virtual MySQL hosts cannot see
other
  customers' databases. (It's more likely that you won't attack
something
  which you cannot see.)
 
  Or am I missing out on something?


 Functionality is still there, but implemented at the place it belongs
to.

 Pay attention on Privlieges tables 4.0.5 uses. You will see there is:

 `Show_db_priv` enum('N','Y') NOT NULL default 'N'

 i.e. User must be granted explicitly this privilege in order to be
able to use:
 SHOW DATABASES;

 Suggested way for setting this Ptivilege is ofcourse command:
 GRANT SHOW DATABASES;

 I hope you will agree that this approach provides much better
flexibility and is
 more natural than mysqld starting option.

 If you still have concerns, please don't hesitate to share them with
us.

 --
   For technical support contracts, visit https://order.mysql.com/
  __  ___ ___   __
 /  |/  /_ __/ __/ __ \/ /Mr. Alexander Keremidarski
[EMAIL PROTECTED]
/ /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Developer
   /_/  /_/\_, /___/\___\_\___/   Sofia, Bulgaria
   ___/   www.mysql.com



 -
 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

Re: MySQL 4.0.5(a) is released

2002-11-29 Thread Peter Zaitsev 
On Friday 29 November 2002 00:32, Stefan Hinz, iConnect \(Berlin\) wrote:
 Dear Lenz,
 
  Removed variable `safe_show_database' as it was not used anymore.
 
 What will ISPs say about this one? They use 'safe_show_database' for their
 MySQL setups, so their customers on virtual MySQL hosts cannot see other
 customers' databases. (It's more likely that you won't attack something
 which you cannot see.)
 
 Or am I missing out on something?

It is not that bad :)

Now safe_show_database is a sort of default. And if you need user which can 
see all databases you can grant him SHOW_DATABASE privelege.

So  ISPs should  be only happy with this change :)


-- 
__  ___ ___   __
   /  |/  /_ __/ __/ __ \/ /Mr. Peter Zaitsev [EMAIL PROTECTED]
  / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Developer
 /_/  /_/\_, /___/\___\_\___/   Moscow, Russia
___/   www.mysql.com   


-
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

Re: MySQL 4.0.5(a) is released

2002-11-28 Thread Stefan Hinz, iConnect \(Berlin\) 
Dear Lenz,

 Removed variable `safe_show_database' as it was not used anymore.

What will ISPs say about this one? They use 'safe_show_database' for their
MySQL setups, so their customers on virtual MySQL hosts cannot see other
customers' databases. (It's more likely that you won't attack something
which you cannot see.)

Or am I missing out on something?

Regards,
--
  Stefan Hinz [EMAIL PROTECTED]
  CEO / Geschäftsleitung iConnect GmbH http://iConnect.de
  Heesestr. 6, 12169 Berlin (Germany)
  Telefon: +49 30 7970948-0  Fax: +49 30 7970948-3


- Original Message -
From: Lenz Grimmer [EMAIL PROTECTED]
To: MySQL announce list [EMAIL PROTECTED]
Cc: MySQL mailing list [EMAIL PROTECTED]
Sent: Wednesday, November 27, 2002 10:41 PM
Subject: MySQL 4.0.5(a) is released


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

MySQL 4.0.5, a new version of the world's most 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.

This is a new beta development release, adding new features and fixing
recently discovered bugs. This will be the last release labelled as beta -
the upcoming MySQL 4.0.6 will be labelled gamma, which emphasizes the fact
that the MySQL 4.0 code base has further stabilized and is becoming ready
for
productive use.

To avoid confusion between the product names of the GPL and non-GPL
(commercial) binaries, MySQL AB has now further refined the new naming
scheme. Starting with MySQL 4.0.5 and onwards, the following binaries will
be
available:

MySQL Standard (GPL)
This is the recommended binary for most users that want to use MySQL under
the
terms of the GNU General Public License (GPL). It includes the InnoDB
Storage
Engine and all default features that are considered stable and useful enough
for general usage.

MySQL Max (GPL)
This is an enhanced version of the Standard GPL package. In addition to the
InnoDB Storage Engine, it includes additional features like the Berkeley DB
(BDB) Storage Engine (certain platforms only) as well as other additional
features that are either not exhaustively tested yet or not required for
most
users, e.g. OpenSSL (where available), User defined functions (UDFs), or
BIG_TABLE support. When these features have matured and proven to be stable
enough, they will be part of future versions of the Standard binaries.
Please
note, that not all of these features are included in all binaries.

MySQL Classic (Commercial License)
Similar to MySQL Standard, but *without* InnoDB and only available as a
commercial licensed version.

MySQL Pro (Commercial License)
Similar to MySQL Standard (*including* InnoDB), but only available as a
commercial licensed version.


- From the 4.0.5 ChangeLog:

Functionality added or changed:

 * Changed handling of last argument in `WEEK()' so that one can get
   week number according to the ISO 8601 specification.  (Old code
   should still work).
 * Fixed that `INSERT DELAY' threads doesn't hang on `Waiting for
   INSERT' when one sends a `SIGHUP' to `mysqld'.
 * Change that `AND' works according to SQL ANSI99 when it comes to
   `NULL' handling. In practice, this only affects queries where you
   do something like `WHERE ... NOT (NULL AND 0)'.
 * `mysqld' will now resolve `basedir' to its full path (with
   `realpath()'). This enables one to use relative symlinks to the
   MySQL installation directory.  This will however cause `show
   variables' to report different directories on systems where there
   is a symbolic link in the path.
 * Fixed that MySQL will not use an index scan on an index that has
   been disabled with `IGNORE INDEX' or `USE INDEX'.
 * Added `--use-frm' option to `mysqlcheck'. When used with `REPAIR',
   it gets the table structure from the `.frm' file, so the table can
   be repaired even if the `.MYI' header is corrupted.
 * Fixed bug in `MAX()' optimization when used with `JOIN' and `ON'
   expressions.
 * Added support for reading of MySQL 4.1 table definition files.
 * `BETWEEN' behaviour changed (*note Comparison Operators::).  Now
   `datetime_col BETWEEN timestamp AND timespamp' should work as
   expected.
 * One can create `TEMPORARY' `MERGE' tables now.
 * `DELETE FROM myisam_table' now shrinks not only the `.MYD' file but
   also the `.MYI' file.
 * When one uses the `--open-files-limit=#' option to `mysqld_safe'
   it's now passed on to `mysqld'.
 * Changed output from `EXPLAIN' from `'where used'' to `'Using
   where'' to make it more in line with other output.
 * Removed variable `safe_show_database' as it was not used anymore.
 * Updated source tree to be built using `automake 1.5' and `libtool
   1.4'.
 * Fixed an inadvertently changed option (`--ignore-space') back to
   the original `--ignore-spaces' in `mysqlclient'. (Both syntaxes
   will work).
 * Don't require `UPDATE' privilege when using `REPLACE'.
 * Allow braces in joins in all positions. Formerly

Re: MySQL 4.0.5(a) is released

2002-11-28 Thread Paul DuBois 
At 22:32 +0100 11/28/02, Stefan Hinz, iConnect (Berlin) wrote:

Dear Lenz,


 Removed variable `safe_show_database' as it was not used anymore.


What will ISPs say about this one? They use 'safe_show_database' for their
MySQL setups, so their customers on virtual MySQL hosts cannot see other
customers' databases. (It's more likely that you won't attack something
which you cannot see.)

Or am I missing out on something?


There is now a SHOW DATABASES privilege in the grant tables.



Regards,
--
  Stefan Hinz [EMAIL PROTECTED]
  CEO / Geschäftsleitung iConnect GmbH http://iConnect.de
  Heesestr. 6, 12169 Berlin (Germany)
  Telefon: +49 30 7970948-0  Fax: +49 30 7970948-3



-
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

MySQL 4.0.5(a) is released

2002-11-27 Thread Lenz Grimmer 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

MySQL 4.0.5, a new version of the world's most 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.

This is a new beta development release, adding new features and fixing 
recently discovered bugs. This will be the last release labelled as beta - 
the upcoming MySQL 4.0.6 will be labelled gamma, which emphasizes the fact
that the MySQL 4.0 code base has further stabilized and is becoming ready for 
productive use.

To avoid confusion between the product names of the GPL and non-GPL 
(commercial) binaries, MySQL AB has now further refined the new naming 
scheme. Starting with MySQL 4.0.5 and onwards, the following binaries will be 
available:

MySQL Standard (GPL)
This is the recommended binary for most users that want to use MySQL under the 
terms of the GNU General Public License (GPL). It includes the InnoDB Storage 
Engine and all default features that are considered stable and useful enough 
for general usage.

MySQL Max (GPL)
This is an enhanced version of the Standard GPL package. In addition to the 
InnoDB Storage Engine, it includes additional features like the Berkeley DB 
(BDB) Storage Engine (certain platforms only) as well as other additional 
features that are either not exhaustively tested yet or not required for most 
users, e.g. OpenSSL (where available), User defined functions (UDFs), or 
BIG_TABLE support. When these features have matured and proven to be stable 
enough, they will be part of future versions of the Standard binaries. Please
note, that not all of these features are included in all binaries.

MySQL Classic (Commercial License)
Similar to MySQL Standard, but *without* InnoDB and only available as a 
commercial licensed version.

MySQL Pro (Commercial License)
Similar to MySQL Standard (*including* InnoDB), but only available as a 
commercial licensed version. 


- From the 4.0.5 ChangeLog:

Functionality added or changed:

 * Changed handling of last argument in `WEEK()' so that one can get
   week number according to the ISO 8601 specification.  (Old code
   should still work).
 * Fixed that `INSERT DELAY' threads doesn't hang on `Waiting for
   INSERT' when one sends a `SIGHUP' to `mysqld'.
 * Change that `AND' works according to SQL ANSI99 when it comes to
   `NULL' handling. In practice, this only affects queries where you
   do something like `WHERE ... NOT (NULL AND 0)'.
 * `mysqld' will now resolve `basedir' to its full path (with
   `realpath()'). This enables one to use relative symlinks to the
   MySQL installation directory.  This will however cause `show
   variables' to report different directories on systems where there
   is a symbolic link in the path.
 * Fixed that MySQL will not use an index scan on an index that has
   been disabled with `IGNORE INDEX' or `USE INDEX'.
 * Added `--use-frm' option to `mysqlcheck'. When used with `REPAIR',
   it gets the table structure from the `.frm' file, so the table can
   be repaired even if the `.MYI' header is corrupted.
 * Fixed bug in `MAX()' optimization when used with `JOIN' and `ON'
   expressions.
 * Added support for reading of MySQL 4.1 table definition files.
 * `BETWEEN' behaviour changed (*note Comparison Operators::).  Now
   `datetime_col BETWEEN timestamp AND timespamp' should work as
   expected.
 * One can create `TEMPORARY' `MERGE' tables now.
 * `DELETE FROM myisam_table' now shrinks not only the `.MYD' file but
   also the `.MYI' file.
 * When one uses the `--open-files-limit=#' option to `mysqld_safe'
   it's now passed on to `mysqld'.
 * Changed output from `EXPLAIN' from `'where used'' to `'Using
   where'' to make it more in line with other output.
 * Removed variable `safe_show_database' as it was not used anymore.
 * Updated source tree to be built using `automake 1.5' and `libtool
   1.4'.
 * Fixed an inadvertently changed option (`--ignore-space') back to
   the original `--ignore-spaces' in `mysqlclient'. (Both syntaxes
   will work).
 * Don't require `UPDATE' privilege when using `REPLACE'.
 * Allow braces in joins in all positions. Formerly, things like
   `SELECT * FROM (t2 LEFT JOIN t3 USING (a)), t1' worked, but not
   `SELECT * FROM t1, (t2 LEFT JOIN t3 USING (a))'. Note that braces
   are simply removed, they do not change the way the join is
   executed.
 * InnoDB now supports also isolation levels `READ UNCOMMITTED' and
   `READ COMMITTED'.  For a detailed InnoDB changelog, see the section
   InnoDB Change History in this manual.

Bugs fixed:

 * Corrected test for `root' user in `mysqld_safe'.
 * Fixed error message issued when storage engine cannot do `CHECK'
   or `REPAIR'.
 * Fixed rare core dump problem in complicated `GROUP BY' queries that
   didn't return any result.
 * Fixed `mysqlshow' to work properly with wildcarded database names
   and with database names that contain