MySQL compatibility observation

Posted: Wed Jan 31, 2007 9:56 pm

Just wanted to say that I released my first module recently, and I really didn't know what to expect. I was kind of ducking under the table. Well the biggest problem so far was that I was inadvertently using MySQL functions and operators that were relatively new. For example, I was calling LAST_DAY() and using the DIV operator. These didn't show up until 4.1.something or later. Well it turns out there are still a lot of people using MySQL 4.0.xx, and my queries would fail for them. I'm just throwing this out as a lesson learned to new module authors.

I remember when I was coding those queries up, and I would read "this was added in 4.1.xx". And I remember thinking to myself "huh, I wonder if that is an issue or not?". Well it turns out it is. Smile

A big thanks to Hitwalker for helping me debug the problems I was having. Groovy

Sells PC To Pay For Divorce Joined: Posts: 5661

no problem gremmy,glad i could help...
but its understandable (from a programmers point of view) that you would use latest techniques available.
but as we know by now maybe 30% of all people can use it....
its all to new.

registered · Posted: Fri Feb 02, 2007 6:35 am

Well, mySQL 4.1.x is actually quite "old". That is the version that we certify RavenNuke on, although, I have to admit, I have no issues with it so far on 5.0.x.

I definitely struggle with this. I really want to use PHP 5.1.x and mySQl 5.0.x as a minimum, but know that I would alienate so many people. Maybe, as RavenNuke 2.10 gets released and people upgrade and/or migrate to it, over time as it is proven out on the higher releases, we can help change that. But, I am just too impatient... Smile

Posted: Fri Feb 02, 2007 6:50 am

good point montego,but thats the thing i discussed with my main host.
And its very clear that to many people work with scripts that isnt compatible with higer mysql and php versions...

nobody should feel bad if they use a lower version..
most things developed are still for lower versions..

and all higher versions aren't bug free.

Posted: Fri Feb 02, 2007 7:15 am

I hear you m8, but... PHP 5.1.x and mySQL 5.0.x ARE stable... Something has to start pushing hosts in that direction...

Posted: Fri Feb 02, 2007 12:58 pm

Yes, and on the PHP front, I would much rather use the OO features in PHP 5 than the rather "tacked on at the last minute" OO features of PHP 4.

Posted: Fri Feb 02, 2007 7:03 pm

What a crap. Use PostgreSQL or something else that is better and has the "new techniques" already for ages.

A host that doesn't install PHP5/MySQL5 is not a host. It is a money maker with some lame excuse to avoid the discussion that he has no clue about servers.

How else am i able to run PHP 4 and PHP 5, MySQL 4 and MySQL 5 on one single server?
The answers are simple and possible in a few different ways, and those are known for ages (you old people think about the PHP 3 vs 4 times when you used .php3 and .php4 files)

Hereby i already gave one clue in the way of extensions. The other way is based on .htaccess where you specify to either loadmodule php5 or php4.

As for MySQL: run multiple servers on different port numbers.

Posted: Fri Feb 02, 2007 7:23 pm

djmaze...

the point is what people have on their server might not run on PHP5/MySQL5.
if i wanna change to a PHP5/MySQL5 enviroment i can do that whenever i want.
the problem wasnt that its not available....
ive chosen to stay on the server lower then PHP5/MySQL5 .. Wink

at some point a moment or date will be picked and then all goes to PHP5/MySQL5...

Posted: Fri Feb 02, 2007 7:29 pm

I understand the point of not running it.

So my point was about those stupids hosts not having a clue about running them both and therefore not giving you the opertunity to take the version you like and providing a hint that a developer can use them all at the same time.

Therefore there shouldn't be any issues when you test them at all.

Posted: Sat Feb 03, 2007 8:21 am

I agree, having the choice would be nice, however the point of the thread is more geared towards what is the most widely used "stack" today by people's hosts. The reality is that if you write something that will only work on the higher versions of PHP/mySQL, just be aware that you may have just chopped off the vast majority of your intended audience.

It all depends on your objectives for release of your code.

I think that is all Gremmie and others are putting out there for newbie PHP/Nuker programmers to keep in mind.

djmaze, your points are very valid (of course!) and are also good for folks to know about. It may take each one of us (at least those who use shared hosting) to start demanding better choices from our hosts!

Posted: Sat Feb 03, 2007 12:21 pm

Yes. I could code all I want in MySQL 5 and PHP 5, but the audience for my module would, sadly, be A LOT smaller. Or so it seems from the emails I got when I released my module.

Posted: Tue Feb 06, 2007 10:30 am

I also struggle with this question.. there are some new time functions in php 5 I'd like to play with.... and it might inspire me to put a little more effort in to learning oo.

But... my comfort zone is still within php 4.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

As far as I know, RavenNuke(tm) is not using any 4.1 only functions. I have tried to avoid that. I think we should be compatible even with 3.23.