[#10460] Problem with external mysql addressbook
Summary Problem with external mysql addressbook
Queue Horde Framework Packages
Queue Version Git master
Type Bug
State Assigned
Priority 2. Medium
Owners jan@horde.org
Requester claude.tompers@restena.lu
Created 2011-08-26 (3710 days ago)
Updated 2011-09-06 (3699 days ago)
Assigned 2011-09-06 (3699 days ago)
Milestone 1.5.0
Patch No

claude.tompers@restena.lu 2011-08-26 11:18:27
When using an external mysql addressbook (different database than the 
HORDE DB), Turba tries to write something into the horde_cache table 
using the external mysql ressource instead of the HORDE DB. This 
happens in browse.php.

Jan Schneider <jan@horde.org> 2011-09-02 16:58:43
I cannot reproduce. How does your backends(.local).php look like?

Jan Schneider <jan@horde.org> 2011-09-02 17:03:30
Nevermind, I forgot to change the Cache backend.

Git Commit <commits@lists.horde.org> 2011-09-02 17:22:39
Changes have been made in Git for this ticket:

Fix creating cache objects for Horde_Db.
We cannot simply pass the current Horde_Db object into the Horde_Cache 
that we pass back to that object, because we might be creating a Horde_Db
object for a completely different SQL configuration than required for
Create a new Horde_Db object with the separate cache configuration 
instead, but
set this object's 'cache' property to avoid an infinite loop.

Bug: 10460

  2 files changed, 7 insertions(+), 1 deletions(-)

Jan Schneider <jan@horde.org> 2011-09-02 17:23:08
This was a bug in Horde_Core.

Git Commit <commits@lists.horde.org> 2011-09-06 07:23:54
Changes have been made in Git for this ticket:

Revert "Fix creating cache objects for Horde_Db."
This reverts commit 6c7b1ce4d9b529822899af05df6b5a00ea414b8d.

Bug #10460

Fixes fatal error that completely prevents viewing of any page.

I am using PostgreSQL as DB driver, files as cache driver. The code
seems to assume that the cache driver will ALWAYS be a SQL DB.  This is
obviously incorrect.

  2 files changed, 1 insertions(+), 7 deletions(-)

Michael Slusarz <slusarz@horde.org> 2011-09-06 07:26:09
As mentioned in ticket, the original fix seems faulty because it 
assumes that we are using DB caching.  At the very least, that fix 
completely breaks installations so it is necessarily reverted until 
properly fixed.