Hi,
MySQL 5.0.2-alpha, a new version of the popular Open Source/Free Software
Database Management System has been released. It is now available in source
and binary form for a number of platforms from our download pages at
http://dev.mysql.com/downloads/ and mirror sites.
Note that not all mirror sites may be up-to-date at this point. If you
cannot find this version on a particular mirror, please try again later or
choose another download site.
This is a snapshot of the alpha development tree, adding new features and
fixing recently discovered bugs.
NOTE: This is an ALPHA release. This build passes most of our test suite
and fixes a lot of reported bugs found in the previous 5.0.1 release.
However, please be aware that this is not a 'standard MySQL release'.
There are still some open critical bugs in our bugs database
(http://bugs.mysql.com/) that affect this release as well. And there are
a number of platforms that are experiencing build issues.
We are actively working to fix these issues and will make a new release
where these are fixed as soon as possible. This snapshot gives you an
opportunity for testing and evaluating the new MySQL 5.0 features for
future products.
Please refer to our bug database at http://bugs.mysql.com/ for more details
about the individual open and resolved bugs in this version.
Changes in release 5.0.2:
Functionality added or changed:
* Warning: Incompatible change! The precedence of NOT operator has
changed so that expressions such as NOT a BETWEEN b AND c are
parsed correctly as NOT (a BETWEEN b AND c) rather than as (NOT a)
BETWEEN b AND c. The pre-5.0 higher-precedence behavior can be
obtained by enabling the new HIGH_NOT_PRECEDENCE SQL mode.
* Added IS [NOT] boolean_value syntax, where boolean_value is TRUE,
FALSE, or UNKNOWN.
* Added several InnoDB status variables. See section 5.2.4
Server Status Variables.
* Implemented the WITH CHECK OPTION clause for CREATE VIEW.
* The SCHEMA and SCHEMAS keywords are now accepted as synonyms for
DATABASE and DATABASES.
* Added initial support for rudimentary triggers (the CREATE TRIGGER
and DROP TRIGGER statements).
* Added basic support for read-only server side cursors.
* mysqldump --single-transaction --master-data is now able to take
an online (non-blocking) dump of InnoDB and report the
corresponding binary log coordinates, which makes a backup
suitable for point-in-time recovery, roll-forward or replication
slave creation. See section 8.8 The mysqldump Database
Backup Program.
* Added --start-datetime, --stop-datetime, --start-position,
--stop-position options to mysqlbinlog (makes point-in-time
recovery easier).
* Made the MySQL server not react to signals SIGHUP and SIGQUIT on
Mac OS X 10.3. This is needed because under this OS, the MySQL
server receives lots of these signals (reported as Bug #2030).
* New --auto-increment-increment and --auto-increment-offset startup
options. These allow you to set up a server to generate
auto-increment values that don't conflict with another server.
* MySQL now by default will check dates and only allow fully correct
dates. If you want to MySQL to behave as default, you should
enable the new ALLOW_INVALID_DATES SQL mode.
* Added STRICT_TRANS_TABLES, STRICT_ALL_TABLES, NO_ZERO_IN_DATE,
NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, and TRADITIONAL SQL
modes. The TRADITIONAL mode is shorthand for all the preceding
modes. When using mode TRADITIONAL, MySQL generates an error if
you try to insert a wrong value in a column. It does not adjust
the value to the closest possible legal value.
* MySQL now remembers which columns were declared to have default
values. In STRICT_TRANS_TABLES/STRICT_ALL_TABLES mode, you now get
an error if you do an INSERT without specifying all columns that
don't have a default value. A side effect of this is that when you
do SHOW CREATE for a new table, you will no longer see a DEFAULT
value for a column for which you didn't specify a default value.
* The compilation flag DONT_USE_DEFAULT_FIELDS was removed because
you can get the same behavior by setting the sql_mode system
variable to STRICT_TRANS_TABLES.
* Added NO_AUTO_CREATE_USER SQL mode to prevent GRANT from
automatically creating new users if it would otherwise do so,
unless a password also is specified.
* We now detect too-large floating point numbers during statement
parsing and generate an error messages for them.
* Renamed the sql_updatable_view_key system variable to
updatable_views_with_limit. This variable now can have only two
values:
+ 1 or YES: Don't issue an error message (warning only) if a
