History of MySQL

The name of MySQL Dolphin logo is sakila, which was selected by the founder of MySQL AB from a large number of names recommended by users in the Dolphin Naming Competition. The winning name was provided by Ambrose Twebaze, an open source software developer from Swaziland, Africa. According to Ambrose, Sakila comes from a Swazi dialect called SiSwati, which is also the name of a small town in Arusha, Tanzania, near Ambrose's hometown of Uganda.

2.MySQL development

The history of MySQL can be traced back to 1979. A man named Monty Widenius works in a small company called TcX, and designs a report tool with BASIC, which can run on a computer with a main frequency of 4M 16KB. Soon after, this tool was rewritten in C language and transplanted to Unix platform. At that time, it was just a very low-level report-oriented storage engine. This tool is called Unireg.

1985, several like-minded young people in Sweden (headed by David Axmark) set up a company, which is the predecessor of MySQL AB. The company didn't develop database products at first, but needed a database in the process of realizing their ideas. They want to use open source products. But there was no suitable choice and no way at that time, so I developed it myself.

At first, they just designed a method of accessing data in index order, which is the predecessor of the core algorithm of ISAM (index order access method) storage engine, and used ISAM combined with mSQL to realize their application requirements. In the early days, they mainly provided data warehouse services for some large retailers in Sweden. In the process of using the system, with the increasing data volume and system complexity, the combination of ISAM and mSQL is gradually overwhelmed. After analyzing the performance bottleneck, they found that the problem was mSQL. As a last resort, they abandoned mSQL and re-developed a set of data storage engines with similar functions, which is ISAM storage engine. You may have noticed that their main customer at that time was data warehouse, which should be easy to understand why MySQL is best at query performance, not transaction processing (with the help of third-party storage engines).

In 1990, some customers of TcX began to request SQL support for their API. At that time, some people thought of using commercial databases directly, but Monty felt that the speed of commercial databases was not satisfactory. So, with the help of mSQL code, he integrated it into his own storage engine. But unfortunately, the effect is not very good. Therefore, Monty is ambitious and determined to rewrite an SQL support himself.

1996, MySQL 1.0 release, small-scale use. 1June 1996, MySQL 3.11.1was released, but there is no 2.x version. At first, only the binary version under Solaris was provided. A month later, the Linux version appeared. At this time, MySQL is still very simple, with no other functions except inserting, updating, deleting and selecting on a table.

In the next two years, MySQL was transplanted to various platforms in turn. At the time of release, the authorization strategy adopted is somewhat different: free commercial use is allowed, but MySQL cannot be released together with its own products. If you want to publish it together, you must use a special license, which means spending money. Of course, business support also costs money. Others are available to users. This special license has brought some income to MySQL, thus laying a good foundation for its sustainable development.

1999-2000, Sweden established a company called MySQL AB. Hired several people to cooperate with Sleepycat to develop Berkeley DB engine. Because BDB supports transaction processing, MySQL began to support transaction processing.

In 2000, MySQL published its own source code and officially entered the open source world by adopting GPL(GNU General Public License) license agreement.

In April 2000, MySQL sorted out the old storage engine and named it MyISAM.

200 1, Heikiki Tuuri suggested to MySQL to integrate their storage engine InnoDB, which also supports transaction processing and row-level locking. So when 200 1 released version 3.23, it already supported most basic SQL operations, and also integrated MyISAM and InnoDB storage engines. The official combined version of MySQL and InnoDB is 4.0.

In June 2004, the classic version 4. 1 was released. From June 5438 to October 2005 10, the milestone version MySQL 5.0 was released. In 5.0, cursors, stored procedures, triggers, views and transaction support have been added. In the version after 5.0, MySQL clearly shows the pace of development to high-performance database.

In 2008, MySQL 16 was acquired by Sun Company.

On April 20, 2009, Oracle acquired Sun Company and MySQL was transferred to Oracle.

MySQL 5.5 and MySQL Cluster 7. 1 were released on April 22nd, 2000.

The MySQL version that can be downloaded in official website now is: 5.5. 18. Oracle re-divided MySQL version into community version and enterprise version. The enterprise edition needs to be charged, of course, charging will provide more functions.