Trying to upgrade from 3.23.27 to 3.23.38 via rpm. The problem is then
Apache/PHP cannot connect to the database (using the mysql routines internal
to PHP), so I'm left having to --force --nodeps a downgrade to keep the
system up. Now, PHP can be compiled to use the current MySQL libraries, but
the last time I had to do that (with an install of MySQL 3.23.37 from binary
tar to a Debian box) a needed MySQL library or two wasn't on the system, and
to get it I had to compile MySQL from the source tar. Okay:
1. Is there a way to just get PHP/Apache to talk to the current MySQL
without recompiling to reference the current MySQL libraries?
2. Does the development rpm actually contain what I'll need to point to if I
_do_ have to recompile everything?
3. Considering that PHP/Apache is one of the most common MySQL front ends,
why isn't this set of problems prominently dealt with in the documentation,
if not avoided through clever programming and/or making sure the PHP team
has early access to any interface changes coming along?
Whit
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
