Home >> Developer Tools >> MySQL

MySQL 5.0.51a

MySQL is a multithreaded, multi-user, SQL Database Management System (DBMS).


MySQL Main Feature:
  • * A broad subset of ANSI SQL 99, as well as extensions.
  • * Cross-platform support.
  • * Stored procedures.
  • * Triggers
  • * Cursors
  • * updatable Views
  • * True VARCHAR support
  • * INFORMATION_SCHEMA
  • * Strict mode
  • * X/Open XA distributed transaction processing (DTP) support; two phase commit as part of this, using Oracle's InnoDB engine
  • * Independent storage engines (MyISAM for read speed, InnoDB for transactions and referential integrity, Archive for storing historical data in little space)
  • * Transactions with the InnoDB, BDB and Cluster storage engines; savepoints with InnoDB
  • * SSL support
  • * Query caching
  • * Sub-SELECTs (i.e. nested SELECTs)
  • * Replication with one master per slave, many slaves per master, no automatic support for multiple masters per slave.
  • * Full-text indexing and searching using MyISAM engine
  • * Embedded database library
  • * Full Unicode support
  • * ACID compliance using the InnoDB, BDB and Cluster engines
  • * Shared-nothing clustering through MySQL Cluster

MySQL Current Version:
MySQL 5.0.51a

MySQL New Version Change Log:
  • Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server with yaSSL enabled and TCP/IP connections enabled, but does not require valid MySQL account credentials. The exploit does not apply to OpenSSL. Note The proof-of-concept exploit is freely available on the Internet. Everyone with a vulnerable MySQL configuration is advised to upgrade immediately.
  • Security Fix: ALTER VIEW retained the original DEFINER value, even when altered by another user, which could allow that user to gain the access rights of the view. Now ALTER VIEW is allowed only to the original definer or users with the SUPER privilege. (Bug#29908)
  • Security Fix: When using a FEDERATED table, the local server could be forced to crash if the remote server returned a result with fewer columns than expected. (Bug#29801)