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

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6673
-----------------------------------------------------------------------
  Ticket             | 6673
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | horde not switching db correctly using horde  
sql session storage and
                     | mysql authentication with persistent connections
  Queue              | Horde Base
  Version            | 3.1.7
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2008-06-13 05:03) wrote:

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.