Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 88873 - mysql support broken in php 4.2.2 release
mysql support broken in php 4.2.2 release
Product: Red Hat Linux
Classification: Retired
Component: php (Show other bugs)
i686 Linux
high Severity high
: ---
: ---
Assigned To: Joe Orton
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-04-15 04:01 EDT by David M Johnson
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-15 13:27:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David M Johnson 2003-04-15 04:01:21 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 

Description of problem:
Having upgraded to RPM to php 4.2.2 following the notification from RHN. PHP 
does not appear to have support of MySQL any more. The output from phpinfo() 
does not show mysql, snmp and other modules even though they appear in the 
configuration information in phpinfo.

When trying to run phpMyAdmin again the MySQL data base it reports that the 
MySQL module is not loaded

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Upgrade to 4.2.2 form the RHN
2. create a phpinfo() test page
3. look at results

Additional info:
Comment 1 Joe Orton 2003-04-15 04:14:04 EDT
What is the output of:

$ rpm -q php php-mysql
$ grep ^extension= /etc/php.ini

Comment 2 David M Johnson 2003-04-15 13:27:03 EDT
This appears to have resolved itself. The module does not appear in the phpinfo
() output, but PHPmyadmin now works. This is following updating the mysql.so 
file from the redhat site.

Is this possibly due to mysql being built in now.

Note You need to log in before you can comment on or make changes to this bug.