MySQL 5 has come out of the alpha development phase with the release of the first public beta, 5.0.3.
- Download page: http://dev.mysql.com/downloads/mysql/5.0.html
The MySQL developer zone is carrying series of articles on the major new features, which include triggers, views and stored procedures.
MySQL AB has released new versions of its flagship products. MySQL 4.1.10 provides several small fixes, including "predefined accounts without passwords for remote users" in the Windows distribtion (presumably in connection with the recent Windows security issue).
Also MaxDB 7.6 Beta has been made available in preparation for the production version release scheduled for the second quarter of 2005.
A worm is on the loose attacking MySQL installations on computers running Windows. This does not appear to be a MySQL exploit; rather one which takes advantage of weak security to use MySQL functions to insert malicious code into the system.
mysqldump utility doesn't provide any inbuilt
facilities for compressing output. This can be a problem if the
disk space available is smaller than the dump's final size.
On Linux and UNIX systems the way round this is to compress
mysqldump's output on the fly, e.g. using the
mysqldump -uroot -pPASSWORD --opt --all-databases | bzip2 -c > mysql-full-dump.bz2
A common problem in MySQL is the comparatively simple act of defining a TIMESTAMP column which has as its default value the timestamp at the time the record is created. In most databases this is simply a case of appending DEFAULT NOW() to the timestamp column.
Beginning with version 4.1.2 MySQL now supports this, albeit as an overlay to the slightly eccentric TIMESTAMP functionality, making life just that little bit easier.
The most prominent new feature of MySQL 4.1 is the introduction of subqueries (also known as subselects), a very welcome addition which brings MySQL's feature set a little closer to that of other databases.
It's possible to modify the way in which MySQL interprets certain parts of SQL, useful when porting queries from other databases. For example, the option PIPES_AS_CONCAT will persuade it to accept || as a concatenation operator rather than as a synonym for OR (see also gotcha 1.12). In 4.1 this facility has been extended considerably.