richandzhaoyan

Exactly! Changing over tomorrow would not be good....

Changing with two to three weeks notice would be fine for me. I know it would mean work to get my sites compatible but its got to be done at some point so just let me know when.

Why do I not prepare now? Well unfortunately I have plenty of other jobs on, its justs a question of prioritising. When I have to switch I will do but at present, on mysql 4 the site works and is taking orders so why waste time making modifications that wont have any visible effect for the customers.

For sure I would think that there would be some good money to be made by programmers who could take on the osC work but I think that judging by some of Vgers posts the switch to mysql5 is going to be a bit harder than changing to php5.

With regards to Knapper's post, I agree with all your comments. The latest version of osC is I believe mysql 5 compatible. The trouble is that anyone running osC will have numerous contributions added, many of which will not be mysql 5 compatible and which prevent users from simply upgrading to the latest version.

Really for myself, rather than doing a lot of work on an outdated vesion of osC, I think I would prefer to use the switch over as an excuse to completely redesign my sites from scratch, possibly trying a different solution to osC altogether but again, this depends on time frames.

UH's problem is that they do have a lot of osC sites hosted on their servers. They have a good reputation for hosting osC sites and as such have to take this into consideration when planning the change. NOT for the sake of the responsible site owners who will be ready but to try and avoid the high number of support tickets they recieved after the recent php5 change, although how they can avoid this when 8 months notice is not enough, I really dont know!

Anyhow, just to confirm, I have no problem with a quicker changeover (from UH's new roadmap it isnt going to be till next year anyway). Tomorrow may be a bit soon but I would be fine with a couple of weeks notice. And I can understand how it must be frustrating for anyone not using osC.

Cheers,
Rich

__________________
Only Dead Fish go with the Flow....
shopping2buyonline.com

pursuit

trouble is, why they have to buy a service which they may not need at all in the first place. dont get me wrong i very much love to have this opportunity but then if you put yourself into the shoe of these site owners you then start to think differently. mysql5 does not offer any tangible benefit at all to an osc shop, although the conversion of mysql4 to 5 is much easier and predictable (but may be time consuming) than forcing an old osc shop to work under register globals off.

Simon

All software needs upgrading eventually, I make a living out of writing software, if nothing ever changed I'd be out of a job fairly fast!

__________________
Freelance PHP Programming
__________________

MrBen

vBulletin have recently posted a development update. It says the new version they are working on (v4) will require MySQL 5.0.22 and PHP 5.2.3 (already sorted on the PHP front). I'm sure there are a few customers with vB forums that will want to upgrade whenever it is released (it is "months" away though).

vBulletin Development Update - August 4th 2008 - vBulletin Community Forum

Ben

__________________
The impossible I can do today, miracles take a little longer

Veterinary Practice Management System by SoftFooding
Internet Data Usage Calculator: Estimate your monthly bandwidth usage for your Internet connection.

Vger

I think that everyone here knows that I don't support switching to MySQL 5 just so that the "developers" amongst us can use it.

However, it has become apparent recently that more software is being released which will not work on MySQL 4, and for this reason we will seriously have to think about switching to MySQL 5 sooner rather than later.

We already have one server which is MySQL 5, but that's our own hosting server and not for customer sites.

Vger

__________________
Working with computers is a bit like getting old - the longer you're around the more wrinkles you find!

VEAdas

My 2 cents: i think we should upgrade.

jaik

It's one of those chicken and egg situations, as it was with PHP 5. Hosting companies don't want to kill back-compatibility, but developers don't want to release code that needs a version no one has. My personal thought is that MySQL 5 is long overdue, so the sooner the better

canuckster

Just a thought — I don't know how practical this would be from UH's perspective — but what about polling UH customers for the best time to make the change?

What I mean is this: suppose UH could say, "We can switch to MySQL5 as early as December 15th, or as late as January 31st. What would be your first and second choices for the switchover week? Click here to reply." — leading to a simple form.

Maybe this seems a bit much, but this is different from the PHP 4->5 switch, where we could effectively experiment with 5 via the change to .htaccess, then revert while fixing any problems; when MySQL changes, it will be a make-it-work-now-or-else situation. (Yes, I know one can test locally, but in my experience the unexpected usually rears its head despite the best efforts against it).

sabian1982

I would like to see an upgrade go through as v5 does work a lot quicker for certain tasks (especially when compiling a database with a fair few thousand entries!)

__________________
Freelance Web Designer