RE: [PHP-DEV] Wierd CVS Build problem with libmysql

From: Date: Mon, 06 Nov 2000 20:39:51 +0000
Subject: RE: [PHP-DEV] Wierd CVS Build problem with libmysql
References: 1  Groups: php.dev php.qa 
Request: Send a blank email to php-dev+get-37300@lists.php.net to get a copy of this message
At 02:55 PM 11/6/00 -0500, Mike Robinson wrote:
Michael Widenius wrote: Another issue: We would like to extend the mysql_connect() and mysql_pconnect() with 2 extra (not required) arguments: path-to-config-file and group This would allow the php program to access all clients connect options (like password, user and connect timeout) that the libmysqlclient library can provide. If the first option is given (and is not the empty string), one should call mysql_options(&mysql, MYSQL_READ_DEFAULT_FILE, path-to-config-file) If the second one is given one should call: mysql_options(&mysql, MYSQL_READ_DEFAULT_GROUP, group) For example: mysql_pconnect("host","db","","/tmp/my.cnf","php"); Would read the [php] and [client] group sections from the /tmp/my.cnf file. What do you think about the above? IMHO, this looks useful. Late last week I thought Zeev was asking for last minute do or die stuff, with a view to putting out 4.0.4. Is this going to affect that, time wise? Maybe it should wait until after 4.0.4?
I think it should wait for after 4.0.4 because I understand this is a non-tested MySQL patch? Also it would mean that our MySQL extension update would also need a bit of time to stabilize (even though it probably would not be a big patch). I think it would be good to get 4.0.4 out the door by next week. The reason why it has been taking so long because there were quite a few open issues raised (most of them have been fixed by now). Are the build problems with the new MySQL client all solved now? I'm also cc'ing the PHP QA guys who might have a better idea of the issues which were raised. Thanks! Andi --- Andi Gutmans <andi@zend.com> http://www.zend.com/

« previous php.dev (#37300) next »