MySQL 4.1.8 vs. 4.0.26 Compatibility

Questions about the MySQL, PostgreSQL, and most other databases, as well as using it with PHP can be asked here.

Moderator: General Moderators

Post Reply
User avatar
Ambush Commander
DevNet Master
Posts: 3698
Joined: Mon Oct 25, 2004 9:29 pm
Location: New Jersey, US

MySQL 4.1.8 vs. 4.0.26 Compatibility

Post by Ambush Commander »

Or, to be more general, 4.0.x - 4.1.x. My server is running an older version of MySQL, 4.0, so I have to accomodate for it. I didn't think there'd be that much of a problem, until my create table queries started failing. After some rooting around, I found out that extensive Unicode support was not added until 4.1... so I have to remove all character set specific code from my table creation SQL...

http://dev.mysql.com/doc/refman/4.1/en/news-4-1-x.html offers a bit of information about the changes, but I'm not exactly sure what all these features do (especially Subqueries and derived views). Can anyone offer any tips for writing 4.0 to 4.1 compatible SQL (5.0 compatibility would be nice but not necessary).

Also... when was FOR UPDATE added to InnoDB?
User avatar
Maugrim_The_Reaper
DevNet Master
Posts: 2704
Joined: Tue Nov 02, 2004 5:43 am
Location: Ireland

Post by Maugrim_The_Reaper »

I switch between MySQL 3, 4.0, 4.1 - sometimes 5, but very rarely.

phpMyAdmin can export a database scheme to be MySQL 3 compatible if its any help - works for my own Unicode database under v4.1 at least. More simply I write SQL the same way (or nearly) as I've always done for MySQL 3. If I need the v4 specific features I make certain they're only used when I can be assured a supporting DBMS will be used - otherwise I'll fall back to MySQL 3 compat.

I'm sure methods vary between developers. MySQL is a barrel of trouble if you go looking for it - I doubt users outside we developers even know differing MySQL versions exists let alone are different...
Post Reply