Multiple database + pconnect issues

[eluser]bAum[/eluser]
It seems that we are talking about two different problems here, let me clarify

What I meant is that having an object for each databse (being able to say $db1->query() and $db2->query()) is very convenient. It is, however, not possible with the usual connection parameters if these two databases happen to be on the same mysql/postgres/.. server.

In that case the connection function will refuse to connect to the same server twice, and so $db1 and $db2 are actually the same. This means that in your code, you explicitly need to change the active database each time you alternate between $db1 and $db2 (by issuing a USE query first). While this might be more optimal, since you have only one open connection instead of two, it will mess up your code if you alternate between $db1 and $db2 very often.

Instead, you can force a reconnect and you'll end up with two connections to the same database server but on different databases ($db1 and $db2 are different). This might be considered a waste of performance, but now your $db1 and $db2 can be used transparently, without the need of clunking your code with USE queries.

A third solution would be to rewrite the db connection driver like the guys at the start of the thread did, but well, you need to do it, you need to maintain it and so on..


As for the persistent connections you are talking about, I am not sure how that affects the "different databases on same database server" issue I just described. The mysql_pconnect method also has the force reconnect parameter, which suggests that it works the same way. However, that doesn't make sense to me, since the doc says that a persistent connection is identified by host, username and password only (not the active database).