Comments on: Should WP drop MySQL 3.23 support?

By: toys

toys — Mon, 23 Jul 2007 20:10:58 +0000

I definitely agree with many of the other guys here – since it is redundant, drop support for it. It doesn’t make sense to continue. Since MySQL AB are dropping support for their product, I don’t think WordPress ought to take on the responsibility of support.

Kudo’s to you guys for keeping support for so long – that’s truly commendable. But I think in this case, you should not worry to much. You should upgrade to receive proper support. This isn’t a windows XP to windows Vista issue… lol.

By: Diario a Borbo · WordPress 2.1 RC 1

Diario a Borbo · WordPress 2.1 RC 1 — Thu, 18 Jan 2007 07:24:46 +0000

[...] se ha abierto un debate/discusión sobre si se debería dar soporte a la versiones 3.23.23 o superior de MySQL en WordPress 2.1 y parece ser que ya han tomado una decisión como cuentan en SigT. Estos requeremientos de MySQL no [...]

By: +++ Wordpress Ticker +++ — Software Guide

+++ Wordpress Ticker +++ — Software Guide — Wed, 17 Jan 2007 23:58:15 +0000

[...] ergeben, dass die wenigsten für den Weitererhalt dieser veralteten MySQL-Version stimmten, daher wurde entschieden, dass für WordPress 2.1 MySQL 4.0 oder höher erforderlich ist. Mit WordPress 2.2 werden nur noch [...]

By: Ryan

Ryan — Tue, 09 Jan 2007 20:21:11 +0000

2.1 doesn’t use MATCH AGAINST. Perhaps a plugin is doing that.

By: kris

kris — Tue, 09 Jan 2007 20:08:27 +0000

wp 2.1 doesn’t currently work with mysql 4 either, it uses mysql 5 only “match” “against” syntax. it could easily be changed to not use mysql 5 only syntax and work with 4 as well though.

By: moeffju

moeffju — Mon, 08 Jan 2007 13:27:25 +0000

Drop 3.x support, the moreso as the 2.0.x series will keep running on 3.x.

Most hosters offer the choice between 4.x and 5.x nowadays, I don’t know anyone still using MySQL 3.

By: pumpkinslayer

pumpkinslayer — Mon, 18 Dec 2006 04:33:29 +0000

Drop it!

WordPress has always maintained security updates of previous versions, so users would in no way have a compromised/unsecure version. If you want the latest release though, you’ll need 4.x or higher.

Keep moving forward…

By: Claude Gelinas

Claude Gelinas — Sat, 16 Dec 2006 04:59:15 +0000

As long as there’s a comprehensive upgrade path, for WordPress, from MySQL 3.x to 4.x, it’s a good choice to move up to 4.x, especially if there are performance advantages.

Bloggers who happen to use MySQL 3.x as their backend database can continue doing so for as long as they want… until they want to use the latest and greatest feature that’ll be developed for use with MySQL 4.x.

By: Bliss

Bliss — Thu, 07 Dec 2006 13:32:47 +0000

Yups. Drop It!. Once its dropped, those never bothering upgrading it will ‘wake up’ a bit with ‘yawn’ n upgrade it.

no harms.

By: Jason Roysdon

Jason Roysdon — Mon, 04 Dec 2006 23:37:27 +0000

I’m running RH’s Fedora Core 3 still:
$ rpm -q mysql
mysql-3.23.58-16.FC3.1

We are planning to upgrade to FC6 shortly which has mysql.i386 5.0.27-1.fc6.

However, upgrades are slow and painful. They take a lot of work and consideration. We don’t just want to drop in a custom mysql RPM, as we need security updates, but we don’t manage that ourselves. That means we take a huge step forward when we move to FC6 and not just mysql is going to be affected.

FC3 is still supported by fedoralegacy.org until FC7-Test1 ships (another month or so at least). Even Fedora has release maintenance/support cycles, and I think it’s totally acceptable for WP to do the same. Just give us all enough warning, and keep maintaining the WP2.0.x cycle for security patches (no new features) once WP2.1 ships to give those some more of us time.

Webpages and blogging is a hobby for me, and not something I have a lot of time to devote on the backend to.