Re: PHP 4.0 Bug #5823: PHP assumes MySQL unix socket is always available

Rasmus Lerdorf wrote: > But it can easily be worked around by providing the path to the unix > domain socket in the mysql_connect() line. My worry is falling back on a > slower mechanism without the user knowing this is happening. This could be solved by the one-time warning message, or (better) by always using the MySQL client library directly, instead of using local PHP copy. MySQL is open source - if you want some changes, contribute the changes back to MySQL, there is no need to distibute slighly modified copy of it. I do not thing that spewing the error messages is right thing in case we are talking about. Particularily because there is currently no way to tell PHP to not try to use the unix socket (so I'm plain stuck without the patch I've send), and for obvious reasons, I would not like to have one. > The size of the binary is completely irrelevant. Sure. Code sharing is. I do not want every piece of software use it's own MySQL client library, I want it all to use the one distributed with MySQL. One of reasons is that I can safely upgrade MySQL, update relevant shared libraries and everything else continues to work, without need to recompile. That's one of the very neat features of shared libraries :) What are the reasons to include MySQL client library in PHP distribution ? Jaromir -- Jaromir Dolecek <jdolecek@NetBSD.org> http://www.ics.muni.cz/~dolecek/ @@@@ Wanna a real operating system ? Go and get NetBSD, damn! @@@@