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

> 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. It is not slightly modified, and it is maintained by the MySQL developers. It is extremely handy to have built-in support on Windows, for example. > 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. Which OS are you on that does not have Unix Domain sockets? And why isn't this a problem better solved in the underlying MySQL client library? Seems to me that you will have to go patch every app that uses MySQL on your system because they will all be using the mysql client library in much the same way PHP does. > > 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 ? It makes installation simpler for people who need to connect to a MySQL database somewhere. They don't need to install the client libs on their own machine. -Rasmus