Re: Change User on a pconnect

I think the hash key would have to be just the hostname, and the structure saved in the hash would need to contain the MySQL link, username & password. The MySQL module would then lookup the connection by hostname and would compare the username/password to the ones stored in the hash's value. If they are different, it would then do a change_user and update the hashed information. What do you think? Andi At 04:32 PM 11/5/99 -0500, Rasmus Lerdorf wrote:

I just added mysql_change_user() to the PHP 3 tree, mostly because someone asked me for it. However, the idea behind the function, and why it was added to MySQL recently was to allow us to maintain a pconnect across different user mysql user ids. This would mean that if we are talking to MySQL-3.23.3 or higher, we would not store the username and password in the hashed_details, but instead just do a change_user. However, I don't want to slow down the pconnect process here with a change_user call that might not be needed. So perhaps we should still store the username/password in hashed_details and let pconnect work the way it has always worked, but have a different puserconnect function or something like that which would do an automatic change_user on a persistent connection and if it fails to authenticate it would not return the connection link identifier to prevent someone from hijacking somebody else's persistent link. Comments? -Rasmus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

--- Andi Gutmans <andi@zend.com> http://www.zend.com/