Comments on: More on PHP5 adoption

By: Nattapol

Nattapol — Thu, 06 Dec 2012 10:31:46 +0000

In the system I was tetnsig on I was using the IN() operator with a list of primary key values, (the PK is just an autoincrement column), so there was an index. The table was ~160k rows, and there was a join of some sort involved, (although the where condition didn’t use anything from the joins, it only had the IN(pk list)). I had an unused column available so I just set it to greater than 0 on the rows I wanted and changed my WHERE to WHERE unusedcol > 0. That got me more speed, strangely enough.As you say, benchmarking, (or at least some real-world tetnsig), is the way to go. You never know when something weird’s going to happen in the database engine, and every production environment is different. I just thought I would share my experience, since it’s not what would be expected, (if it was expected, I would never have written the query with an IN() in the first place!).

By: Tony

Tony — Wed, 25 Jul 2007 10:33:55 +0000

Further to this, I just got burned purchasing software that had system requirements of “PHP 4.1 and later” and “MySQL 4.1 and later”, I purchased it, and was then told “don’t be dumb of course we didn’t mean MySQL 5 and PHP5!! If we’d meant PHP 5 we’d have put it in the requirements” my argument was that PHP5 has now been around for 3 years and I had no reason to believe that it wasn’t a part of the “later” specification (as I would have, for instance were I assuming PHP6 was supported. Anyway the long and short of it is I’m about £250 out of pocket with no likelihood of getting a refund. Moreover the software company has done nothing at all to modify or clarify their specs, which leads me to believe they make good money from this. C’est la vie!!. The moral of this story, PHP5 is not later than PHP4 and apparently no one supports it or uses it (except me!!)