In PHP 5 there will be a new extension which gives the full
power Mysql 4 provides. There will not be any such support
in PHP 4.

This snapshot has it:
http://snaps.php.net/php5-200303191630.tar.gz

(use --with-mysqli and --without-mysql)

OTOH, it should be possible to use the mysql 4.0.12 too..
I'm checking this out.

And the (new) mysqli extension requires MySQL 4.1 anyway...

-Tal

Since MySQL has made the 4.0.12 it production version, how far behind is PHP v5.x?  It kind of makes MySQL v4.x usless to PHP websites until PHP has the capability to support MySQL v4.x, since alot of sites use PHP + MySQL.  Any idea when PHP will have a version that will support MySQL v4.x?

-Greg

Just tested this myself, if everything is installed correctly, PHP 4.3.x compiles and works fine with Mysql 4.0.x.

I find this really hard to believe since this has happened on several of our test machines.  I am using the RPM distro of MySQL and simple configs for PHP as you can see above.  So to call this ticket "bogus" I think is premature, but your call.  Hope you don't see any more of these issues in the future!

p.s.: I am not an amature in the Linux world and I know how to configure a system so the statement "if everything is installed correctly" wasn't really necessary.  I posted this to be a help, not to be belittled.

PHP 4.3.1 works for me with MySQL 4.0.12. I have the RPMs of MySQL installed and I compiled PHP 4.3.1 from source. No problems.

Maybe your --with-mysql path is wrong.

I am using the same confige statement for the 4.0.12 installation as I am for the 3.23.55-1 in my php config.  I am at a loss since I have noticed this on 5 machines now all have different hardware, the only thing that is similar is the kernel, php, openssl, and mysql.

When I install 4.0.12 (MySQL) i can't even use the natice mysql support built into php.  Any ideas to see what's up?

I have exactly the same problems. Is anybody found a solution. My websites stop working after upgrading to MySQL 4.0.12. Please help.

Since this has been confirmed by several of my colleges and the post from "jbernier at dalcom dot ca" as a real issue, I have re-opened this ticket.  Please see if there is a fix for this issue, or if we need to change our config.  I have confirmed this with 5 of my colleges.

Works fine here, with latest CVS snapshot and self compiled
Mysql 4.0.12.

Try with shorter configure line, maybe something else is 
causing the problem.
(like this: ./configure --disable-all --with-mysql=/usr)

Sniper, I understand that it works for you.  But you stated you are using the latest CVS and self compiled MySQL.  That is not the original issue and I want to stay on track.

The issue is that the RPM installation of MySQL will not work with the self-compiled version of PHP.  Two people have posted to this saying they are having the same issue, but you insist on saying this is bogus.  I will not use a CVS version on production machines, nor should anyone.  So what do we need to do so that you will take this issue seriously?

I thought the purpose of open source products was for people to work together to make a product better, but in this case it seems our needs to make the product better are being ignored.

Which RPMs have you installed? You need to have the libraries and header files installed too to get the build work..

Did you uninstall the old mysql 3.23 version before installing that new one? Are you sure it's not just a conflict between old and new version of mysql?

And I say again: This is NOT any bug in PHP. Please ask further support questions on e.g. php-install@lists.php.net

OK, I will try this one more time.  As several postings have confirmed, this is an issue.  Can someone please work on a fix so that we can move forward with using the newest production releases of PHP?

It seems that two postings from "azza at sbcglobal dot net" didn't get posted or were removed so I am reposting them.

Posting #2:
I am unclear why this has been set to bogus vs open.

(1) A significant number of other parties are having this issue.
(2) The failure to reproduce the error does not mean the error does not exist. 
(3) The installation process for php and mysql is quite varied, thus unlesss one tests all major installation scenarios no conclusion may be drawn. 
(4) As shown in my previous post - several rpms show a requirement of libmysqlclient.so.10. The correction is to use libmysqlclient.so which has a symlink to the current version, which is libmysqlclient.so.12.

Thus, a) the bug is not bogus, b) the correction may be simple and c) failure to correct the error may have significant negative consequences.

Posting #1:
Same Issue:
I agree that working together is the means for resolving this issue. 

(1) php-mysql-4.3.1-rbt.rh8.1.i386.rpm shows requirement of libmysqlclient.so.10  
http://www.aucs.org/rpmcenter/details/php-4.3.1-for-apache-1.3.x/php-mysql-4.3.1-rbt.rh8.1.i386.rpm.html

(2) php-mysql-4.2.2-8.0.7 RPM for i386 shows requirement of 
libmysqlclient.so.10 http://rpmfind.net/linux/RPM/redhat/updates/8.0/i386/php-mysql-4.2.2-8.0.7.i386.html

What should be in the code is a reference to libmysqlclient.so which is a symlink to the current version - libmysqlclient.so.12.

This may be a major issue if it crashes a large number of sites. Take a look at how libmyssqlclient.so is configured on your system.

Come on..if you can't get it to work, don't automatically
assume that it's a bug in PHP. (which this REALLY IS NOT!)

Thank you for your response.

I am assuming nothing.

What I have asserted is that use of a direct or symlink to libmysqlclient.so.10 is causing a problem. This ownership of this issue balances between (1) mysql, (2) rpm packagers, and (3) php. My objective was not to assert blame, but to identify a significant issue. The fact is that the environment has changed with the new production release of mysql 4.0.12, which is causing a problem (bug) since php-mysql is dependent on libmysqlclient.so.10 versus libmysqlclient.so (which has a link to the current version).

This issue seems to be related to mnogosearch PHP module and MySQL 4.x.  If I remove the --with-mnogosearch it will compile fine.

Not sure where to go from here as I need --with-mnogosearch

Try latest mnogosearch and latest php.
And dont forget to recompile mnogosearch and php after mysql upgrades.