Tickets :: Comment on [#6673] horde not switching db correctly using horde sql session storage and mysql authentication with persistent connections

* Your Email Address
* Spam protection	Enter the letters below: .__..___.. ..___.__ \| \| \| \|\ \|[__ [ __ \|__\| \| \| \\|\| [_./
Comment	> I thought it would check if a mysql connection exists already and > whether is uses the same database as specified in the DB::connect() > call. But that's probably a bit too much magic. Instead it calls > mysql_connect() and uses the new_link parameter for that if specified. > > > > This opens a whole can of worms though, because there could be a lot > of other places where we don't do all database operation > sequentially. But we can't simply request a new link in each SQL > driver. That could easily open a dozen connections per request.
Attachment
Watch this ticket