On Tue, 2003-05-06 at 17:45, Thomas Robinson wrote: > On Tue, 2003-05-06 at 17:29, Michael Smith wrote: > > probably because now that debugging is on it shows the error, but > > doesn't stop the program... > > > > I can see how that might work but I switched off debugging now and it > still works! ?? > What I meant was before I fixed the file access problem, I switched off debugging and it still worked - anyway it works now...8) t. > > -Michael > > On Tue, 2003-05-06 at 03:45, Thomas Robinson wrote: > > > On Tue, 2003-05-06 at 11:57, Thomas Robinson wrote: > > > > On Tue, 2003-05-06 at 11:39, Thomas Robinson wrote: > > > > > On Mon, 2003-05-05 at 23:12, Jesse Keating wrote: > > > > > > On Monday 05 May 2003 15:05, Thomas Robinson wrote: > > > > > > > I'm using: > > > > > > > php-4.2.2-17 > > > > > > > php-mysql-4.2.2-17 > > > > > > > MySQL-3.23.55-1 > > > > > > > > > > > > > > The MySQL is from the MySQL site, in other words, not the Red Hat rpm. > > > > > > > (This was not a problem under RH8 BTW). > > > > > > > > > > > > > > Any help is appreciated. > > > > > > > > > > > > You might need to rebuild the php source rpm against the new mysql. Mysql's > > > > > > rpm may not put files in the same places that Red Hat's rpm does. > > > > > > > > > > Ok, so I've 'down graded' to the default mysql on shrike. I now have the > > > > > following installed: > > > > > > > > > > mysql-3.23.54a-11 > > > > > php-mysql-4.2.2-17 > > > > > perl-DBD-MySQL-2.1021-3 > > > > > php-4.2.2-17 > > > > > mysql-server-3.23.54a-11 > > > > > perl-DBI-1.32-5 > > > > > httpd-2.0.40-21.1 > > > > > > > > > > Am I missing something for PHP+MYSQL to work properly? > > > > > > > > > > I can access the database with mysql client but still I get an error > > > > > through my web (php) interface. All of the site was working perfectly > > > > > under RH8. It's now broken under RH9. I can't spot what the problem is. > > > > > > > > > > Has anyone else had problems with php+mysql being upgraded from RH8 to > > > > > RH9? Any help is appreciated. > > > > > > > > > > Thanks, > > > > > > > > > > t. > > > > > > > > BTW the function phpinfo() works fine and indicates that > > > > /etc/php.d/mysql.ini is being parsed. > > > > > > > > # cat /etc/php.d/mysql.ini > > > > ; Enable mysql extension module > > > > extension=mysql.so > > > > > > > > # locate mysql.so > > > > /var/lib/mysql/mysql.sock > > > > /usr/lib/php4/mysql.so > > > > > > > > help! :-/ > > > > > > > FYI I switched on debugging in /etc/php.ini and it all came to life! > > > There was an error though where the application could not write to a > > > logging file however the database was accessible despite that! Weird...I > > > only switched on debugging and it worked! (I also fixed the file access > > > problem - it's still working...wierdness... > > > > > > now to see if MySQL 4.0 works! :D > > > > > > t. > > > > > > -- > > > __--__-- Mind your own business, Spock. I'm sick of your halfbreed > > > interference. > Should I do my BOBBIE VINTON medley? We should have a Vollyballocracy. We elect a six-pack of presidents. Each one serves until they screw up, at which point they rotate. -- Dennis Miller
