Bug in Mysql 5.0.51a-community? (Wordpress: posts in reverse order)

[rzderich]

Hello

Today we receive a customer case related with wordpress and Mysql version 5.0.51a-community.

Under Wordpress posts are suddenly appearing in reverse order, these bug was described to be Mysql related as shown in these bug:

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

wordpress post related with these:

http://wordpress.org/support/topic/154622

We sould fix these, how can we upgrade from whm to a newer version of mysql ? any work around?

Regards

Roy.

[cpanelkenneth]

5.0.51a is the latest community release.

[Infopro]

Fixes:

For people running older versions of WordPress, upgrade to the latest version. Newer versions are not as susceptible to this issue, however certain edge cases will still exhibit the problem.

[VeZoZ]

It's a bug in MySQL and even though that is the case I don't think it should be happening on application that write SQL properly anyways.

In most other database engines the way the query is setup that causes this is not even valid.

[cpanelkenneth]

If you are running EDGE, we downgraded MySQL 5 to 5.0.45 and are examining our options. The MySQL report states this regression is fixed in 5.0.52, which is an un-released build (at least an un-release community build).

[rzderich]

Thank you guys,

One more question, From cpanel inc. point of view: is these just an mysql issue with the latest communitie release? Have we (cpanel users, cpanel developers) make any mistake?

i ask these because many wordpress users are talking about these bug and they suggest "hosting companies" make a mistake of some sort here.

Best Regards

Roy.

[cpanelkenneth]

The mistake here is a lot of finger pointing.

MySQL changed the way a certain combination of SQL parameters were handled in 5.0.51.

Wordpress happened to use that certain combination.

That certain combination is actually senseless, and won't work on other Database servers.

For whatever reason, MySQL decided to revert the behavior, hence reporting this matter as fixed in 5.0.52 (and corresponding versions in 5.1, 5.2, 6.0, etc).

The community edition is still 5.0.51a, which doesn't have this fix. The Enterprise version is newer and has the fix.

Some/Many ISPs/Webhost providers updated to 5.0.51a to close several security issues.

The bug report and fix was done in November 2007.

From the above you can draw your own conclusion as to the current state and options. For our part we applied the patch to 5.0.51a that 'resolves' the issue and are currently testing it.