Page 1 of 1
Webhost won't upgrade to 4.1
Posted: Mon Nov 21, 2005 11:08 pm
by Ambush Commander
My Webhost (ICDSoft) won't upgrade to MySQL 4.1. This is a major blow to my efforts for i18n, as 4.1 added extensive unicode support. They say that 4.0 is more stable and making the change would cause lots of compatibility problems (old applications, etc). I say bah.
What should I do?
Posted: Mon Nov 21, 2005 11:13 pm
by Charles256
get a new host. if your satisfaction was gaurenteed demand they upgrade or you want a refund since you aer NOT satisfied.. worth a try..
Posted: Tue Nov 22, 2005 6:15 am
by Maugrim_The_Reaper
4.0 is standard. Won't any 4.1 upgrading because of compatibility, and/or that it needs mysqli (I think) from PHP5.
Its a double whammy, don't expect a solution outside a small minority of shared hosts, or a dedicated server you can configure as you please...
Posted: Tue Nov 22, 2005 2:06 pm
by trukfixer
well teh biggest issue is simply a matter of a change in how mysql stores passwords between 4.0 and 4.1 Debian is now making mysql 4.1 standard on all upgrades - you dont need php5 or mysqli for 4.1 - the only issue is in how mysql's password() function works , we easily work around that by first:
Code: Select all
select old_password('whatever_pass');
and take the value it gives and do our database grants , and any php code that does a mysql query using password() needs the function changed to use old_password() in the code, to port over to mysql 4.1 . other than those two issues, we have had no problems upgrading to mysql 4.1
Bri!
Posted: Tue Nov 22, 2005 2:06 pm
by Ambush Commander
Hmm, Maugrim The Reaper, is that really true? I have access to two other hosting provider accounts, Bluehost and Dreamhost, and both use MySQL 4.1.
Edit - I know about the password issue: it was my biggest issue when I was setting up MySQL locally. But it can be done.

Posted: Tue Nov 22, 2005 2:18 pm
by Burrito
4.1 does NOT require mysqli for php 5.
Internally here we have 4.1 running on several servers wtih php 5 and have not had any issues (using mysql only).
I *think* the biggest problem (from the host's perspective) is the collation incompatiabilites between 4.1 and ealier versions.
Posted: Tue Nov 22, 2005 9:43 pm
by d3ad1ysp0rk
Oh stop whining, my company's test server runs 3.0.

Posted: Wed Nov 23, 2005 11:36 am
by Ambush Commander
my company's test server runs 3.0
Haha... well, I guess I'll have to live without it for now.
Posted: Thu Nov 24, 2005 8:37 am
by twigletmac
The stability argument for 4.0 went away when 4.1 became the production release and is even less convincing now that 5.0 is production. Host is just lazy.
Mac
Posted: Thu Nov 24, 2005 8:39 am
by Grim...
twigletmac wrote:Host is just lazy.
That's not fair. If the host upgraded, there's a chance that suddenly everyone's code on the server will stop working due to depreciated methods.
Posted: Thu Nov 24, 2005 8:45 am
by fastfingertips
I'm wondering when they will up to version 5 since i really need stored procedures

Posted: Thu Nov 24, 2005 10:21 am
by twigletmac
Grim... wrote:twigletmac wrote:Host is just lazy.
That's not fair. If the host upgraded, there's a chance that suddenly everyone's code on the server will stop working due to depreciated methods.
You have to upgrade at some point, IIRC MySQL only support two versions at a time and currently they are 4.1 and 5.0. I appreciate that 4.1 would break people's login scripts where they've been (incorrectly) using MySQL's PASSWORD() function. However, if a host knows what the major issues will be then giving plenty of warning and advice should be acceptable. I just don't think the stability argument is a good one especially given that 4.0 is no longer supported.
Mac
Posted: Thu Nov 24, 2005 1:05 pm
by Ambush Commander
I just don't think the stability argument is a good one especially given that 4.0 is no longer supported.
Actually, that's not true: according to the docs, MySQL 4.0 is "Recent, still supported". Unless you and I are talking about different types of support.
I suggested making a dual setup, were the client could chose with version to use, but they said it would be too difficult to do.
Here's the funny thing: they won't offer PHP5 because it is unstable, but their version of PHP is 4.4.2-dev (something I've never heard of). And nonetheless, ICDSoft is one of the most stable hosts I've been with out of all three I've tried. Dreamhost has mysteriously gone AWOL once before, and Bluehost has a penchant for using cutting edge software (4.4.0 and all those variable reference issues).
Posted: Thu Nov 24, 2005 1:36 pm
by Ree
Definately get another host. It's no argument for 4.0, 4.1 has a very nice unicode support which I would be dead without. From my own experience, my host had 4.0 installed by default and when I asked 'look, where's unicode support?' they kindly suggested an upgrade to 4.1 themselves. IMO it's just a matter of your host's willingness to help you and keep you as their client.