php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #30923 MySQL Client API version stagnant
Submitted: 2004-11-28 23:41 UTC Modified: 2004-11-29 05:33 UTC
From: mfurdyk at takingitglobal dot org Assigned:
Status: Not a bug Package: MySQL related
PHP Version: 4.3.9 OS: RH 7.3
Private report: No CVE-ID: None
View Developer Edit
 [2004-11-28 23:41 UTC] mfurdyk at takingitglobal dot org 
Description:
------------
I'm trying to upgrade the Client API version, and I've upgraded mySQL, deleted the old libraries, and installed the new 4.1.7-Shared and devel packages, but with --with-mysql=user and --with-mysql=/path/to/mysql, the old client API version still sticks around.

With a new server I've installed, it pops up to 4.1.7 fine.



Reproduce code:
---------------
Here's my build:

'./configure' '--with-mysql=/usr' '--with-apxs=/usr/local/apache/bin/apxs' '--with-zlib' '--with-gd=/usr/local/lib' '--with-jpeg-dir=/usr/local/bin' '--with-png-dir=/usr/lib' '--enable-inline-optimization' '--with-curl' '--disable-debug' '--with-mcrypt=/usr/local/src/libmcrypt-2.5.7' '--with-mhash' '--enable-ftp' '--enable-mbstring'

Expected result:
----------------
Upgrade to 4.1.7

Patches

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2004-11-28 23:43 UTC] mfurdyk at takingitglobal dot org 
updated summary...kept old one.
 [2004-11-29 00:10 UTC] amt@php.net 
If you want to use the new features of MySQL 4.1+, like the new binary protocol, you need to use PHP 5 and the MySQLi extension. (MySQLi, not MySQL.)

You cannot use the new client protocol with PHP 4.
 [2004-11-29 00:13 UTC] mfurdyk at takingitglobal dot org 
No, I don't (at this point) care about using those features, I just want to know why the Client API version is setting at 3.X -- does this matter? It just seems weird, and thought it might explain some random mySQL errors (unable to save result set) that someone suggested were due to incorrect Client API.

--

In terms of mySQLi, is there a way to have the existing mysql_query / mysql_fetch_assoc use the mysqli variants without doing a huge find/replace on all code?
 [2004-11-29 02:48 UTC] edink@php.net 
You probably have some rogue mysql headers around. Make sure to get rid of them all before installing new version.

--with-mysql=/path/to/mysql should work fine with the new client library.
 [2004-11-29 05:33 UTC] mfurdyk at takingitglobal dot org 
Which files does it look for specifically? I think I've done a relatively thorough uninstall
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Aug 17 07:01:28 2024 UTC