| 8:09 pm on Mar 26, 2013 (gmt 0)|
Goodness. People are still on MySQL 4? MySQL 5 was released Dec 24, 2003. That's 10 years ago. Granted, it took some time to become stable, but it's been stable for quite some time.
- last MySQL 4.x release: 2008
- last Apache 1.x release [EOL]: 2010
And yet, who's on Apache 1.3?
| 12:56 pm on Mar 27, 2013 (gmt 0)|
I wonder what percentage this will affect? You have to have had a database created before they started automatically installing MySQL 5 databases, and they don't say in the FAQ when they started doing this.
| 5:50 pm on Mar 27, 2013 (gmt 0)|
For most hosts this is dependent on CPanel (not sure if 1&1 uses CPanel or not though).
Anyway, CPanel stopped supporting MySQL 4 with the 11.32 release (Dec 4, 2012) and announced the change on Sept 11, 2012.
| 5:52 pm on Mar 27, 2013 (gmt 0)|
|Per the MySQL Support Lifecycle policy, extended support for MySQL 4.1 ended on December 31, 2009. MySQL users are encouraged to upgrade to a current production release of MySQL. |
| 10:18 pm on Mar 27, 2013 (gmt 0)|
Funny how the announcement makes it sound like letting customers be responsible for the migration is a big benefit. "At their leisure..." :)
I'm sure there are loads of users who have no clue as to what version of MySQL they are running, or even what MySQl is.
A better approach would have been to identify customers with active MySQL 4 databases and proactively offer to assist them in the transition.
| 10:50 pm on Mar 27, 2013 (gmt 0)|
"1and1" and "better approach" in the same post. LOL. No kidding. I've never heard of 1and1 doing anything proactive.
I do like their website builder TV commercial in the USA. Makes it look easy and all SEO friendly.
| 11:52 pm on Mar 27, 2013 (gmt 0)|
|A better approach would have been to identify customers with active MySQL 4 databases and proactively offer to assist them in the transition. |
Yes. At the very least 1and1 could have limited the announcement to those who were actually affected. My hosting accounts weren't affected but I still received the announcement, causing me about an hour of anguish.
| 9:38 pm on Mar 28, 2013 (gmt 0)|
They also don't warn you that you'll run into problems if you continue to use their default php version (4) when you upgrade to MySQL 5