EMS logo

Навигация по продуктам

выберите Ваш продукт

Наш партнерский статус

Microsoft Certified Partner
Oracle Certified Partner
Embarcadero Technology Partner

Новости SQL индустрии

Все SQL новости

29/03/2005
MySQL 5.0.3-beta released.

A new version of MySQL Community Edition 5.0.3-beta Open Source database management system has been released. This version now includes support for Stored Procedures, Triggers, Views and many other features. 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 the first Beta release in the 5.0 series. All attention will now be focused on fixing bugs and stabilizing 5.0 for later production release.

NOTE: This Beta release, as any other pre-production release, should not be installed on ``production'' level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has done its best to ensure a high level of quality, protect your data by making a backup as you would for any software beta release.

Please refer to the 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.3:

Functionality added or changed:

  • New privilege CREATE USER was added.
  • Added support for AVG(DISTINCT).
  • InnoDB: Upgrading from 4.1: The sorting order for end-space in TEXT columns for InnoDB tables has changed. Starting from 5.0.3, InnoDB compares TEXT columns as space-padded at the end. If you have a non-unique index on a TEXT column, you should run CHECK TABLE on it, and run OPTIMIZE TABLE if the check reports errors. If you have a UNIQUE INDEX on a TEXT column, you should rebuild the table with OPTIMIZE TABLE.
  • InnoDB: Commit after every 10,000 copied rows when executing ALTER TABLE, CREATE INDEX, DROP INDEX or OPTIMIZE TABLE. This makes it much faster to recover from an aborted operation.
  • From the Windows distribution, predefined accounts without passwords for remote users ("root@%", "@%") were removed (other distributions never had them).
  • Added the CREATE ROUTINE and ALTER ROUTINE privileges, and made the EXECUTE privilege operational.
  • The LOAD DATA statement was extended to support user variables in the target column list, and an optional SET clause. Now one can perform some transformations on data after they have been read and before they are inserted into the table. For example:
        LOAD DATA INFILE 'file.txt' INTO TABLE t1 (column1, @var1)
           SET column2 = @var1/100;
  • InnoDB: Relaxed locking in INSERT...SELECT, single table UPDATE...SELECT and single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog is used and isolation level of the transaction is not serializable. InnoDB uses consistent read in these cases for a selected table.
  • VARCHAR columns now remember end space. A VARCHAR() column can now contain up to 65535 bytes.
  • Added the FEDERATED storage engine. See section 14.6 The FEDERATED Storage Engine.

Bugs fixed:

  • Fixed bug creating user with GRANT fails with password but works without.
  • REPAIR TABLE did not invalidate query results in the query cache that were generated from the table.
  • Stored functions that used cursors could return incorrect results.

And many more...

Source: dev.mysql.com

twitterfacebook