Why was MySQL named "toy database" from 4.0 to 5.1"

MySQLFrom the "toys" in developers' hands to the "most popular in the world" today Open source Database", The process is accompanied by the product version upgrade and the addition of some new features (especially the enterprise database function. Now, with the perfect development of MySQL 5.0, few have called MySQL a "toy Database. The rich features of MySQL meet the needs of many users. The recent actions of Oracle show that they pay great attention to MySQL-Oracle has repeatedly expressed its intention to acquire MySQL.

MySQL product roadmap
Let's start with the more influential MySQL version products and take a look at the upgrade of MySQL.

For MySQL 4.0
MySQL 4.0 was released in March 2003. This version gives new MySQL-based applications a wider range of applications. However, MySQL 4.0 does not support stored procedures, triggers, server pointers, or views. MySQL 4.0 is developed from MySQL 3.23 and has greatly improved compared with MySQL 3.23. It is mainly applicable to Web sites. At this time, MySQL is not an enterprise-level database.

The following are major new features of MySQL 4.0:
FULLTEXT index: the most important thing to expect is the FULLTEXT index.

FULLTEXT creates an index for a text field, providing a powerful and flexible mechanism for executing a Boolean search for this index. Based on general development experience, developers usually have to create indexes and access text data, while FULLTEXT indexes are much better than imagined.

Many solutions are limited to full-text indexes. FULLTEXT indexes do not have such restrictions and allow developers to add or split phrases.

Ansi SQL union: supports the ansi SQL UNION statement, which collects query results into a result set.

Multi-table operations: you can perform multi-table UPDATE and DELETE operations.

New statements: new non-standard statements (such as IDENTITY and truncate table) that other DBMS users are familiar with and new functions such as FOUND_ROWS, these functions return the number of records that can be returned without the LIMIT clause.

InnoDB storage engine: as a standard feature of the server at that time, the InnoDB storage engine became an additional option in version 4.0. InnoDb is a table type that allows ACID compatibility with transactions, rather than the default MyISAM table type. It can accelerate general usage, but is not very useful for key operations.

InnoDB tables use the row-level locking feature, which means that only the record is locked for updates to a record, rather than the entire table. When you select to access a large number of databases (for most Web sites), locking the entire table is quite fast, but when the number of inserts and updates is close to the number of options, the speed is slow. For a long time, criticism of MySQL has been concentrated on the security and consistency of MyISAM tables. InnoDB tables compatible with ACID have gone a long way to solve these problems.