From 4.0 to 5.1 Why is MySQL named 'Toy Database'_PHP Tutorial

MySQL has changed from a "toy" in the hands of developers to today's "the world's most popular open source Database ”, the process is accompanied by product version upgrades and the addition of some new features (especially enterprise database features). Now, with MySQL 5.0 being perfectly developed, few people call MySQL a "toy database" anymore. MySQL's rich functions meet the needs of many users. Oracle's recent actions show that they take MySQL very seriously - Oracle has expressed its intention to acquire MySQL several times.

MySQL product roadmap
Let us start with the more influential versions of MySQL products and take a look at the updates of MySQL.

MySQL 4.0
MySQL 4.0 was released in March 2003, which enabled new MySQL-based applications to become more widely used. But in version 4.0, MySQL does not support stored procedures, triggers, server-side pointers, or views. MySQL 4.0 was developed from 3.23. It has been greatly improved compared to the 3.23 version. It is mainly suitable for Web sites. At this time, MySQL is not yet an enterprise-level database.

The following are the main new features of MySQL 4.0:
FULLTEXT index: Perhaps the most anticipated by users is the FULLTEXT index.

FULLTEXT creates an index on a text field, providing a powerful and flexible mechanism for performing Boolean searches on the index. According to general development experience, developers usually have to create indexes and access text data, and FULLTEXT indexes are much better than imagined.

While many solutions are limited to full-word indexes, FULLTEXT indexes have no such limitation, allowing developers to add or split phrases.

ANSI SQL UNION: Supports ANSI SQL UNION statement, which collects query results into a result set.

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

New statements: Added some non-standard new statements familiar to other DBMS users (such as IDENTITY and TRUNCATE TABLE), as well as new functions such as FOUND_ROWS(), which can return without a LIMIT clause The number of the record.

InnoDB storage engine: The InnoDB storage engine was a standard feature of the server at the time and became an additional option in version 4.0. InnoDb is a table type that allows ACID-compliant transactions instead of the default MyISAM table type, which can speed up general use, but is not very useful for critical operations.

InnoDB tables use row-level locking, which means that updates to a record only lock that record, not the entire table. Locking the entire table is fairly fast when the selection accesses a large database (as is the case for most web sites), but slower when the number of inserts and updates approaches the number of options. Criticisms of MySQL have long focused on security and consistency issues with MyISAM tables, and ACID-compliant InnoDB tables go a long way toward solving these problems.

http://www.bkjia.com/PHPjc/630964.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/630964.htmlTechArticleMySQL has changed from a "toy" in the hands of developers to today's "the most popular open source database in the world", among which The process is accompanied by product version upgrades, as well as some new features (especially...