HOMEPAGE: www.mysql.com
TYPE: (Open Source)
DOWNLOAD: MySQL 5.0.89
SIZE: 38 MB
GOOGLE HITS: 22 Millions +
MySQL delivers enterprise features, including:
- Partitioning to improve performance and management of very large database environments
- Row-based/Hybrid Replication for improved replication security
- Event Scheduler to create and schedule jobs that perform various database tasks
- XPath Support
- Dynamic General/Slow Query Log
- Performance/Load Testing Utility (mysqlslap)
- Improved! Full Text Search (faster, new dev templates)
- Improved! Archive engine (better compression, more features)
- Improved! User session and problem SQL identification
- Improved! MySQL embedded library (libmysqld)
- Additional INFORMATION_SCHEMA objects
- Faster data import operations (parallel file load)
- ACID Transactions to build reliable and secure business critical applications
- Stored Procedures to improve developer productivity
- Triggers to enforce complex business rules at the database level
- Views to ensure sensitive information is not compromised
- Information Schema to provide easy access to metadata
- Pluggable Storage Engine Architecture for maximum flexibility
- Archive Storage Engine for historical and audit data
+ Bugs fixed:
- Privileges for stored routines were ignored for mixed-case routine names. (Bug#48872) See also Bug#41049.
- Building MySQL on Fedora Core 12 64-bit would due to errors in comp_err. (Bug#48864)
- DISTINCT was ignored for queries with GROUP BY WITH ROLLUP and only const tables. (Bug#48475)
- Loose index scan was inappropriately chosen for some WHERE conditions. (Bug#48472)
- A bad typecast could cause query execution to allocate large amounts of memory. (Bug#48458)
- mysql_secure_installation did not work on Solaris. (Bug#48086)
- When running mysql_secure_installation, the command would fail if the root password contained multiple spaces, \, # or quote characters. (Bug#48031)
- InnoDB did not disallow creation of an index with the name GEN_CLUST_INDEX, which is used internally. (Bug#46000)
- Use of InnoDB monitoring (SHOW ENGINE INNODB STATUS or one of the InnoDB Monitor tables) could cause a server crash due to invalid access to a shared variable in a concurrent environment. (Bug#38883)
- Output from mysql --html did not encode the <, >, or & characters. (Bug#27884)
0 comments:
Post a Comment