upCASE wrote:The problem seems to be solvable by dumping the entire DB, change the contents to UTF8 and store it again. Unfortunately this is a rather lengthy process and means downtime for the forum. Still I see no other way to tackle this, so we should decide on the when, who and how...
Sounds a dangerous task...Sorry for the troubles brought up to you guys...
Regards,
Utensil
In fascination of creating worlds by words, and in pursuit of words behind the world.
We will have to look into this coming Easter. It is time again to make a backup of the DB, but the only tedious task is that this needs to be done on a command line, and upCASE or me have to monitor this closely. I can't promise that I have the time for it though, my long weekend off is already fully booked, but I'll try.
Utensil wrote: Sounds a dangerous task...Sorry for the troubles brought up to you guys...
Nevermind
To be honest I expected something like this in the long run as I observed this in other projects as well. Changing the encoding might lead to undesired results, it should have been planed before setting up the forum, but neither Jorg nor me thought about this when we started.
The only problem is that it takes time to do this. Plus it will result in some downtime for the forum. If we had physical access to the server it could be done fast, but downloading and re-uploading alone takes a lot of time now, seeing that the DB has grown to an impressive size
Jorg: Could you mail me the login again? Seems like I lost it during the process of setting up my new PC. I still have access to the web console. I'll check what I can do from there.
OS: OpenSuSE, Ubuntu, Win XP Pro
wx: svn
Compiler: gcc 4.5.1, VC 2008, eVC 4
"If it was hard to write it should be hard to read..." - the unknown coder
"Try not! Do. Or do not. There is no try." - Yoda
Sounds a dangerous task...Sorry for the troubles brought up to you guys... 
