MySQL Notes

1 | 2 | 3 | 4 | Index

Beginning with version 5.0.3, MySQL now includes a "real" TRUNCATE command for InnoDB tables, similar to that provided by Oracle and PostgreSQL.

George-Cristian Bīrzan (gcbirzan {at} constanta dot rdsnet dot ro) wrote to point out that it is affected by the following interesting gotcha:

Posted at 2:43 PM

As a follow-up to this article, MySQL has - according to this CNET report - renewed the InnoDB contract inherited by Oracle when it purchased the Finnish company.

MySQL CEO Marten Mickos is quoted as saying "Oracle told us that it's business as usual--they don't want to slow us down, and they will fix bugs" - which on the face of it is good news for anyone with a long term investment in InnoDB technologies.

The article does not say whether Oracle will fix some of the more fundamental issues with InnoDB's MySQL engine.

In related news, MySQL is pushing ahead with development of its own transactional storage engine following its acquisition of Netfrastructure, one of the original InterBase developers and a member of the Firebird project.

Posted at 2:14 PM

Many of the gotchas in pre 5.0 MySQL versions stem from the fact that operations silently failed without any type of error message or warning. That situation has improved with 5.0, with explicit warnings being emmitted on some operations, such as when data is truncated, making it easier to catch potential problems.

However, with DDL operations (e.g. DROP TABLE) in a transactional context, there are still no warnings which would alert the user to potential problems. Of course, in MySQL DDL operations are by nature not transactional, but sometimes it is easy to forget this.

Posted at 7:41 AM

This is the first gotcha I've found for the current 5.0 series.

"INSERT INTO" seems to accept the phrase "VALUE" as equivalent to the more usual "VALUES". While I'm not sure whether this is standard SQL, I've never encountered it before and can find no reference to this syntax on the documentation page at http://dev.mysql.com/doc/refman/5.0/en/insert.html.

For example:

Posted at 6:57 AM

October 25, 2005

MySQL | MySQL 5.0 production release

MySQL 5.0 is finally ready for the big time with the release of the first general availabilty version 5.0.15 following a long period of testing.

The addition of many new features such as stored procedures, triggers, views and cursors has finally brought MySQL onto the same playing field as other RDBMS products, both proprietary and open source, and puts it in a position to expand into the "enterprise" database market.

It is also a good reason to finally get around to updating (and hopefully reducing) the MySQL Gotchas - watch that space.

Posted at 7:46 AM

MySQL 5 has come out of the alpha development phase with the release of the first public beta, 5.0.3.

The MySQL developer zone is carrying series of articles on the major new features, which include triggers, views and stored procedures.

Posted at 8:48 PM

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.

Posted at 8:27 AM

February 8, 2005

MySQL | MySQL and Windows Security

Following the recent bot attacks against poorly secured MySQL installations on Windows (not a MySQL vulnerability), MySQL AB has published an article detailing how to best secure a MySQL server running on Microsoft platforms:

Posted at 10:11 PM

1 | 2 | 3 | 4 | Index