hi, this sounds reasonable. But why don't the "connection aliases" keep the current db they are working on and if needed, switch back - transparently to the user? The current implementation only confuses people.
-daniel ----- Original Message ----- >From : Rasmus Lerdorf [mailto:[EMAIL PROTECTED]] Sent : Montag, 22. April 2002 Subject: [PHP-DEV] Major Bug in multiple MySQL Connections? > It's not a silly behaviour. Database connections are a very limited > resource, much more so than open files, and time after time we saw code > that would open up multiple identical connections for no reason > whatsoever. This is especially true of large apps that are able to swallow > other apps. Like PHP-Nuke with various plug-in modules. If you patch 3 or > 4 different things together that all talk to a DB on localhost, you do not > need to go through the code and unify the database handling to avoid > having 4 separate connections per request. PHP automatically optimizes > that for you. Opening a new connection is also extremely expensive, much > more so than a simple db switch call on an existing one. > -Rasmus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
