[Tickets #13463] Re: Horde_Core-2.13.1 breaks SQL database access

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13463
------------------------------------------------------------------------------
  Ticket             | 13463
  Updated By         | jcblanco at fi.upm.es
  Summary            | Horde_Core-2.13.1 breaks SQL database access
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


jcblanco at fi.upm.es (2014-09-04 09:27) wrote:

No, sorry. With de new Db.php the error is the same.

I think that the problem is caused by calling setLogger without a  
prior SetCache when you pass $cache as false.

Without knowing if this is not the intended behaviour or if this my  
break some other thing with this change:

         if ($cache && !isset($config['logger'])) {
             $ob->setLogger($this->_injector->getInstance('Horde_Log_Logger'));
         }

the error goes away,

I know that in this situation the logger instance is not atached to  
the individual read and write db objects

I know that the performance is worse with SQL Session Handler but we  
have Horde installed in two diffent systems and if we use Standard PHP  
Session files we have locking problems, and we haven't been able of  
getting the "Distribute Cache Table" option to work