Thanks to everyone that offered all the valuable suggestions. SImply
replaced the shared-community with shared-compat and all seesm fine.
Will live with, or deal with, the missmatch in php libraries later, but
for now everything seems to work.
Thanks again to everyone that offered such detailed and helpful
suggestions :)
Gary Smith wrote:
> You are right. I misspoke regarding mysql -> php -> apache hell. It happens
> anytime an interface changes.
>
> ________________________________________
> From: Mark [admin@stripped]
> Sent: Thursday, May 07, 2009 5:57 AM
> To: mysql@stripped
> Subject: RE: Problems After MySql 5.1.34
>
> Gary wrote:
>
>
>> Welcome to the hell that is php + apache + mysql. If you upgrade your
>> MySql (especially major versions 5.0 => 5.1) you will also need to
>> recompile php against the new MySql client libs. We've had very
>> limited success trying to get it to work otherwise.
>>
>
> Well, you don't actually have to recompile PHP entirely, of course: just
> its mysql.so extension.
>
> @TS: Other than that, you basically need to recompile *everything* (or its
> mysql dynamic libraries) when you upgrade MySQL. This includes Perl, btw;
> so you'd need to build DBD:mysql as well (same for Python, etc).
>
> Walter wrote:
>
>
>> Any (major)upgrade of mysql client requires the dependent subsystem to
>> upgrade also. Anything else would be careless since you do not know if the
>> interface has changed.
>>
>
> Actually, you *do* know: that's what the changelog is for. :) When C
> header changes are made, an upgrade is in order. If not, when upgrading
> between minor versions, say, from 5.0.51 -> 5.0.67 (just an example), you
> won't need to recompile all system-wide MySQL client extensions. I've done
> this many times, without issue: you just need to be absolutely sure no
> header changes were made (when in doubt, recompile).
>
> I recently upgraded to 5.1.34 as well; and it was indeed a hell. :) It's
> working just fine, but I spent several hours recompiling MySL client
> stuff; without doing so, your apps will likely behave erratically, or just
> segfault altogether.
>
> This isn't a MySL hell exclusively, btw. You'll get the same issue
> upgrading PostgreSQL, or BerkeleyDB, etc. It's just the nature of the
> beast.
>
> - Mark
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
>
>
--
_____________________________________________
Johnny Stork
Open Enterprise Solutions
"Empowering Business With Open Solutions"
http://www.openenterprise.ca
Mountain Hosting
"Secure Hosting Solutions for Business"
http://www.mountainhosting.ca
