Brion Vibber wrote:
Constans, Camille (C.C.) wrote:
We could convert all tables except old, the biggest and the longest. And running a script which convert old later. Old will be in broken iso-8859 for a few day. I wrote a small php script to convert old from iso-8859-1 to utf-8.
That would be really problematic,
I don't think it would.
it would interfere with user contributions lists and history,
Other than having slightly broken edit summaries for a few days, I'm not sure what problems you are referring to?
and you'll have to be very careful to avoid double conversions.
That won't be a problem. It is trivial to check if something is already in UTF-8 or ISO-8859-1. Checking for this has the added advantage of reducing database load by not converting things that are plain ASCII (and thus don't require conversion) anyway.
diffs, etc, could cause data corruption on reversions (auto and manual),
I don't see that as a problem either. I picture the script would take one page at a time and convert its entire history. Once it's finished with it, it can also check cur to see if someone just by pure coincidence happened to revert something at that particular moment, which is highly unlikely anyway.
I'd recommend strongly against it.
What alternative do you recommend? Prolonged downtime?
Timwi