MySQL 5.1.54
MySQL AB - (Open Source)
MySQL is a successful open source database used in most web applications, e-commerce and online transaction processing.
MySQL is one of the world's most famous and used open source database. The software can be used to manage web applications, e-commerce and online transaction processing since MySQL database incorporates support those transactions. It is also commonly associated with PHP when it comes to managing websites.
With standard JDBC , ODBC, and Net, the developer can choose the programming language. MySQL has the advantage of working with almost all the popular operating systems and communicate easily with programming languages ​​such as C, C + +, VB, C #, PHP, Python, Ruby, Java, Perl, Eiffel, etc.MySQL replication allows you to create profitable applications. In addition, it enables the development of typologies replication complex and massive chain.Its reliability and robustness, performance, ease of use makes MySQL have more success than anticipated.
- Title:
- MySQL 5.1.54
- File Size:
- 38.9 MB
- Requirements:
- Windows 9x / 2000 / XP / Vista / Windows7 / Windows8
- Language:
- en-us
- License:
- Open Source
- Date Added:
- 14 Dec 2010
- Publisher:
- MySQL AB
- Homepage:
- http://www.mysql.com
- MD5 Checksum:
- 5A47267D2601355DBE45909A008B98F0
# Functionality added or changed:
* Support for the IBMDB2I storage engine has been removed.
* The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5.
# Bugs fixed:
* Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables.
* InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time.
* Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash.
* Several compilation problems were fixed.
* Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion.
* Queries executed using the Index Merge access method and a temporary file could return incorrect results.
* The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation.
Screenshots
Related software
Adobe Flash Professional 15.0.0.173
Aptana Studio 3.6.1
ArgoUML 
Blue Griffon 2.3.1
Cheat Engine 6.4
Dreamweaver CS5.5
Firebird 4.0.2.2816-0
Inno Setup 6.0.4
NetBeans IDE 12.4
Notepad++ 7.6.3 for PC Windows3.6/5 from 65 users