Tag Archive for 'MySQL'

MySQL 5.1.43 released

Sun released MySQL 5.1.43.

Changelog

Continue reading ‘MySQL 5.1.43 released’

MySQL 5.5.1-m2 released

MySQL 5.5.1 milestone 2 has been released.

Release Notes

Continue reading ‘MySQL 5.5.1-m2 released’

Cobalt works again

Yesterday I`ve managed to get my new Cobalt to boot.

I`ve installed Strongbolt OS 1.0.6 on the machine and upgraded to Strongbolt 2.

This upgrade included a new bootrom kernel (2.6.23.8-i586), which includes some changes to be able to boot from a USB device.

Strongbolt 2 still uses CentOS 4 as backend.

Later this week I will put some effort into it to make the machine boot BlueOnyx 5.4, which is based on CentOS 5.4
By having a newer CentOS version I also have a newer kernel and the ability to use newer packages.
I can`t wait to get MySQL 5.5 and PHP 5.3 on the machine.

Another thing I still have to do is to buy another Cisco Serial cable to connect the two routers to my webserver.

MySQL 5.1.42 released

Sun released MySQL 5.1.42.

Release Notes

Continue reading ‘MySQL 5.1.42 released’

MySQL 5.0.89 released

Sun released MySQL 5.0.89

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)

Downloads can be found at http://dev.mysql.com/downloads/mysql/5.0.html