Atomicorp

A MySQL bug is affecting Wordpress and I have 5.0.51-1.el4.art installed...

According to some google searches there is a bug in 5.0.51 that....

---Start Quote---
As far as I have understood it (and I'm by no means an SQL guru, so I could be wrong here), the GROUP BY has preference over the ORDER BY. Once the result is grouped, it would be ordered within each group. Now the ID column is an auto-increment column, so each group consists of only one post and therefore it doesn't get ordered.

Previously, MySQL apparently knew that a GROUP BY on an auto-
increment column doesn't make sense and optimized it away. With the
new MySQL version this doesn't happen anymore. I don't know if this
a MySQL bug, but even if it is it has an effect on WordPress that's rather severe. And we can't tell the usual user to upgrade his MySQL, because that's usually done by the provider in rather larger intervals. After having a quick look at the change log[1], I think it's this change that causes this effect:

http://bugs.mysql.com/bug.php?id=30596

Greetings,
Johannes

http://dev.mysql.com/doc/refman/5.0/en/ ... -0-51.html

If you read this you can see at the bottom in links to [2] where a
fix to this issue was introduced for mysql 5.0.52.

So we shouldn't need to do anything - this is a straight mysql bug!
---End Quote---

Scott, any word on a new art MySQL =)

yeah I was testing out 5.0.54 the other day and I had a really bizarre plesk issue come up during an upgrade. Ive only tested that on C4 so far, so it could be something specific to 4. I was using the package from CentOSplus, anyone else give that a shot?

Later today I was goign to fire up my test server and look into centos plus...

Yeah I am running Centos 4.4, PHP 5.2.5(art), MySql 5.0.51-1(art), Plesk 8.3....

scott wrote:yeah I was testing out 5.0.54 the other day and I had a really bizarre plesk issue come up during an upgrade. Ive only tested that on C4 so far, so it could be something specific to 4. I was using the package from CentOSplus, anyone else give that a shot?

I just want to warn everybody about this. Since MySQL 5.0.54 there is some issues with comments. I just upgraded one server (CentOS 4) from Plesk 8.2.1 to 8.3.0 using MySQL 5.0.58. The upgrade failed because of this and I'm now stuck somewhere between 8.2 and 8.3 (no problem so far however, and I will soon upgrade to 8.4).

If you are using 8.2 (or lower), upgrade to 8.4 directly or downgrade mysql (< 5.0.54) if you want to upgrade to a previous Plesk release.

More info about the issue here:
http://kb.parallels.com/en/3546