Originally posted by Corpse
MySql 5?
Collapse
X
-
Well, yes, it does not work out of the box.
But I've managed to write a compatibility patch, all you need is to replace all the occurences of the reserved mySQL 5 keywords in the table names and perhaps fix a couple of other glitches. Don't remember exactly what it was.
Other than that, I can confirm that I've successfully converted it to UTF-8 with mySQL 5 (need this for national characters) and as far as I remember I only had to change all of the hardcoded ISO occurences to UTF-8.
For a good alternative you might wish to try SMF, which supposedly works with mySQL 5 or else IPB 2.2.2 which does work with mySQL 5.0 out of the box.Comment
-
The MySQL version that we'd be upgrading to would likely be 5.0.27 although this could change as time goes by.
It does scare me that developers STILL have not made their scripts compatible with MySQL 5. It's not a difficult task by any means and most code works perfectly without any changes.Comment
-
I folowed some info about compatibility problems and noticed that there are some issues regarding that MySQL 5 radicaly changed some stuff. to mek thing worse, that does not produce visible error notices, but simply server does some things differently. One of the issues is related to TIMESTAMP fields.Comment
-
Yeah I think upgrading to 5.x would be a great idea because of the new features it offers. Not to mention old scripts usually run fine and if not it's an easy fix.
The internet is an evolving creature- we can keep up the pace or be left behind in the dust.Comment
-
Comment
-
Comment
Comment