MySQL

MySQL 5.5.37

MySQL AB
開源軟體

MySQL 為目前最流行的資料庫查詢系統。而 MySQL 主要是以速度、耐用性、易用性為目標,廣泛被企業使用。

  • 支援 MS SQL、Excel、MS Access、XML、CSV 等格式,導入至 MySQL。
  • 較不常需要維護,可節省管理成本。
  • 可保護好您資料庫,發現被不明來源複製則會中斷。
  • 可建立業務應用,確保可靠度及安全性。
  • 為 ACID 特性(原子性、一致性、隔離性、持久性),使軟體達到可靠。

軟體資訊
檔案版本 MySQL 5.5.37
檔案名稱 mysql-5.5.37-win32.msi
檔案大小 33.51MB
系統 Windows 9x / 2000 / XP / Vista / Windows 7 / Windows 8 / Windows 10 / Windows 10 64-bit
支援語系 Multiple languages
軟體類型 開源軟體
更新日期 2014-03-28
更新日誌

# Functionality Added or Changed
* On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime.
# Bugs Fixed
* InnoDB: A regression introduced by Bug #14329288 would result in a performance degradation when a compressed table does not fit into memory.
* InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay.
* InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion.
* InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value.
* InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs.
* InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080
* InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page))
* InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value.
* Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication.
* Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead.
* Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual).
* Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument.
* A shared libmysqld embedded server library was not built on Linux.
* While printing the server version, the mysql client did not check for buffer overflow in a string variable.
* Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights.
* DROP TRIGGER succeeded even with the read_only system variable enabled.
* Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit.
* Due to a race condition, it was possible for two threads to end up with the same query ID for different queries.
* When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message.
* MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing.
* A deadlock error occurring during subquery execution could cause an assertion to be raised.
* The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed.
* For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs.

作者 MySQL AB
官網 http://www.mysql.com

  • realtime statistics server for PHP using MySQL as a read-only interface. ... Links for pinba-engine-mysql-5.5 ... dep: mysql-server-core-5.5 (>= 5.5.37).
    MySQL
    Debian -- Details of package pinba-engine-mysql-5.5 in sid
    https://packages.debian.org
  • MySQL Community Edition is a freely downloadable version of the world's most popular open source database that is supported by an active community of open ...
    MySQL
    Download MySQL 5.5.37 - FileHippo.com
    http://filehippo.com
  • 10 Jul 2016 ... Latest Updates PHP 7.0.8, 5.6.23, and 5.5.37, MySQL 5.5.50. Here are updated packages in the Yum repository: PHP 7.0.8 for RHEL/CentOS ...
    MySQL
    Latest Updates PHP 7.0.8, 5.6.23, and 5.5.37, MySQL 5.5.50
    https://webtatic.com
  • 28 Mar 2014 ... MySQL 5.7.16 (64-bit). Requirements: Windows XP64 / Vista64 / Windows 7 64 / Windows 8 64. User Rating: Click to vote. Author / Product:.
    MySQL
    MySQL 5.5.37 (64-bit) Download for Windows / FileHorse.com
    http://www.filehorse.com
  • MySQL Community Edition is a freely downloadable version of the world's most popular open source database that is supported by an active community of open ...
    MySQL
    MySQL :: Download MySQL Community Server
    https://dev.mysql.com
  • ... in MySQL 5.5.39 (2014-07-31, General Availability) · Changes in MySQL 5.5. 38 (2014-05-30, General Availability) · Changes in MySQL 5.5.37 (2014-03-27, ...
    MySQL
    MySQL :: MySQL 5.5 Release Notes
    https://dev.mysql.com
  • InnoDB: A regression introduced by Bug #14329288 would result in a performance degradation when a compressed table does not fit into memory.
    MySQL
    MySQL :: MySQL 5.5 Release Notes :: Changes in MySQL 5.5.37 ...
    https://dev.mysql.com
  • Changes in MySQL 5.5.37 (2014-03-27, General Availability) · Changes in MySQL 5.5.36 (2014-01-31, General Availability) · Changes in MySQL 5.5.35 ...
    MySQL
    MySQL :: MySQL 5.5 Release Notes :: Changes in MySQL 5.5.43 ...
    https://dev.mysql.com
  • 2015年12月7日 - Changes in MySQL 5.5.37 (2014-03-27, General Availability) · Changes in MySQL 5.5.36 (2014-01-31, General Availability) · Changes in ...
    MySQL
    MySQL :: MySQL 5.5 Release Notes :: Changes in MySQL 5.5.47 ...
    https://dev.mysql.com
  • Changes in MySQL 5.5.37 (2014-03-27, General Availability) · Changes in MySQL 5.5.36 (2014-01-31, General Availability) · Changes in MySQL 5.5.35 ...
    MySQL
    MySQL :: MySQL 5.5 Release Notes :: Changes in MySQL 5.5.49 ...
    https://dev.mysql.com
  • 2016年6月2日 - Changes in MySQL 5.5.37 (2014-03-27, General Availability) · Changes in MySQL 5.5.36 (2014-01-31, General Availability) · Changes in ...
    MySQL
    MySQL :: MySQL 5.5 Release Notes :: Changes in MySQL 5.5.50 ...
    https://dev.mysql.com
  • Changes in MySQL 5.5.37 (2014-03-27, General Availability) · Changes in MySQL 5.5.36 (2014-01-31, General Availability) · Changes in MySQL 5.5.35 ...
    MySQL
    MySQL :: MySQL 5.5 Release Notes :: Changes in MySQL 5.5.51 ...
    https://dev.mysql.com
  • Changes in MySQL 5.5.37 (2014-03-27, General Availability) · Changes in MySQL 5.5.36 (2014-01-31, General Availability) · Changes in MySQL 5.5.35 ...
    MySQL
    MySQL :: MySQL 5.5 Release Notes :: Changes in MySQL 5.5.53 ...
    https://dev.mysql.com
  • Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.5. 37 and earlier, and 5.6.17 and earlier, allows remote authenticated users to ...
    MySQL
    Mysql Mysql : List of security vulnerabilities - CVE Details
    https://www.cvedetails.com
  • Security vulnerabilities of Oracle Mysql version 5.5.37 List of cve security vulnerabilities related to this exact version. You can filter results by cvss scores, years ...
    MySQL
    Oracle Mysql version 5.5.37 : Security vulnerabilities - CVE Details
    https://www.cvedetails.com