Use the below code to display the award image on your website:
MySQL 4.0 further increases the speed of MySQL in a number of areas, such as bulk INSERTs, searching on packed indices, creation of FULLTEXT indices as well as COUNT(DISTINCT).
The table handler InnoDB is now offered as a feature of the standard MySQL server, including full support for transactions and row-level locking.
MySQL 4.0 will support secure traffic between the client and the server, greatly increasing security against malicious intrusion and unauthorised access. Web applications being a cornerstone of MySQL use, web developers have been able to use SSL to secure the traffic between the the end user browser and the Web application, be it written in PHP, Perl, ASP or using any other web development tool. However, the traffic between the development tool and the mysqld server process has been protected only by virtue of them being processes residing on computers within the same firewall. In MySQL 4.0, the mysqld server daemon process can itself use Secure Sockets Layer (SSL), thus enabling secure traffic to MySQL databases from, say, a Windows application residing outside the firewall.
Our German, Austrian and Swiss users will note that we have a new character set latin_de which corrects the German sorting order, placing German Umlauts in the same order as German telephone books.
Features to simplify migration from other database systems to MySQL include TRUNCATE TABLE (like in Oracle) and IDENTITY as a synonym for automatically incremented keys (like in Sybase). Many users will also be happy to learn that MySQL now supports the UNION statement, a long awaited standard SQL feature.
In the process of building features for new users, we have not forgotten requests by the community of loyal users. We have multi-table DELETE statements. By adding support for symbolic linking to MyISAM on the table level (and not just database level as before), as well as by enabling symlink handling by default on Windows, we hope to show that we take enhancement requests seriously. Functions like SQL_CALC_FOUND_ROWS and FOUND_ROWS() makes it possible to know how many rows a query would have returned without a LIMIT clause.
