Software-update: MySQL 6.0.3 alpha

MySQL is een krachtige opensource databaseserver die met name populair is als website- en forumdatabase. Op het forum hebben de ontwikkelaars van MySQL de eerste alphaversie van de 6.0.3-tak aangekondigd. De nieuwe testversie kan via deze pagina voor een groot aantal besturingssystemen gedownload worden. De 6-serie wordt ontwikkeld rondom de nieuwe storage engine Falcon, die voluit The Falcon Transactional Storage Engine wordt genoemd. Falcon wordt ontwikkeld als vervanger van InnoDB en biedt ondersteuning voor onder meer partitioning en record-based replication. Gedetailleerde informatie over de werking van de nieuwe storage engine kan gevonden worden in dit driedelige document van Robin Schumacher, Director of Product Management van MySQL. Een algemene beschrijving van de nieuwe mogelijkheden die MySQL 6 te bieden heeft, kan gelezen worden in dit nieuwsbericht. Hieronder kan gelezen worden wat de developers over MySQL 6.0.3 alpha hebben geschreven:

Dear MySQL users,

The MySQL 6.0.3-alpha, a new version of the MySQL database system with the new Falcon transactional storage engine and several other enhancements, has been released.

The MySQL 6.0.3-alpha is available in source and binary form for a number of platforms from our download pages at

http://dev.mysql.com/downloads/mysql/6.0.html

and mirror sites. Note that not all mirror sites may be up to date at
this point in time, so if you can't find this version on some mirror,
please try again later or choose another download site.

The list of new features in MySQL 6.0:

http://dev.mysql.com/doc/refman/6.0/en/mysql-nutshell.html

The MySQL 6.0 Reference Manual is at:

http://dev.mysql.com/doc/refman/6.0/en/

We welcome and appreciate your feedback, bug reports, etc.:

http://forge.mysql.com/wiki/Contributing

MySQL 6.0 is currently an Alpha release and should not be used in
production environments. It is provided only for testing and evaluation of new features.

Enjoy!
Calvin

Versienummer	6.0.3 alpha
Releasestatus	Alpha
Besturingssystemen	Windows 9x, Windows NT, Windows 2000, Linux, BSD, Windows XP, Linux x86, macOS, Solaris, UNIX, Windows Server 2003, Windows XP x64, Windows Server 2003 x64, Linux AMD64, Windows Vista, Windows Vista x64
Website	MySQL
Download	http://dev.mysql.com/downloads/mysql/6.0.html
Licentietype	Voorwaarden (GNU/BSD/etc.)

Reacties (2)

[Verwijderd]

*

Incompatible Change: Aliases for wildcards (as in SELECT t.* AS 'alias' FROM t) are no longer accepted and result in an error. Previously, such aliases were ignored silently. (Bug#27249)
*

Incompatible Change: Several columns were added to the INFORMATION_SCHEMA.ROUTINES table to provide information about the RETURNS clause data type for stored functions: DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH, NUMERIC_PRECISION, NUMERIC_SCALE, CHARACTER_SET_NAME, and COLLATION_NAME.

This change produces an incompatibility for applications that depend on column order in the ROUTINES table because the new columns appear between the ROUTINE_TYPE and DTD_IDENTIFIER columns. Such applications may need to be adjusted to account for the new columns.
*

Sinhala collations utf8_sinhala_ci and ucs2_sinhala_ci were added for the utf8 and ucs2 character sets. (Bug#26474)
*

If the value of the --log-warnings option is greater than 1, the server now writes access-denied errors to the error log (for example, if a client username or password is incorrect). (Bug#25822)
*

Added the PARAMETERS table to INFORMATION_SCHEMA. The PARAMETERS table provides information about stored function and procedure parameters, and about return values for stored functions.

Bugs fixed:

*

Incompatible Change: DROP TABLE now is allowed only if you have acquired a WRITE lock with LOCK TABLES, or if you hold no locks, or if the table is a TEMPORARY table.

Previously, if other tables were locked, you could drop a table with a read lock or no lock, which could lead to deadlocks between clients. The new stricter behavior means that some usage scenarios will fail when previously they did not. (Bug#25858)
*

Incompatible Change: GRANT and REVOKE statements now cause an implicit commit, and thus are prohibited within stored functions and triggers. (Bug#21975, Bug#21422, Bug#17244)
*

MySQL Cluster: Adding a new TINYTEXT column to an NDB table which used COLUMN_FORMAT = DYNAMIC, and when binary logging was enabled, caused all cluster mysqld processes to crash. (Bug#30213)
*

MySQL Cluster: After adding a new column of one of the TEXT or BLOB types to an NDB table which used COLUMN_FORMAT = DYNAMIC, it was no longer possible to access or drop the table using SQL. (Bug#30205)
*

The server crashed on optimization of queries that compared an indexed DECIMAL column with a string value. (Bug#32262)
*

The server crashed on optimizations that used the range checked for each record access method. (Bug#32229)
*

When comparing a BLOB value that was null, memory corruption could occur casuing the server to crash. (Bug#32191)
*

Deleting a large number of records could sometimes take a significant amount of time. (Bug#27946)
*

Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:
o

For key_buffer_size, values larger than 4GB are allowed on 64-bit platforms.
o

For join_buffer_size, sort_buffer_size, and myisam_sort_buffer_size, values larger than 4GB are allowed on 64-bit platforms (except Windows, for which large values are truncated to 4GB with a warning).

In addition, settings for read_buffer_size and read_rnd_buffer_size are limited to 2GB on all platforms. Larger values are truncated to 2GB with a warning. (Bug#5731, Bug#29419, Bug#29446)

[Killemov]

Hmm, jammer dat een changelog ontbreekt ...