| Summary | Selecting SQL Cache on initial Horde config results in SQL Error |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Bug |
| State | No Feedback |
| Priority | 2. Medium |
| Owners | |
| Requester | bklang (at) horde (dot) org |
| Created | 3/26/11 (5493 days ago) |
| Due | |
| Updated | 5/18/11 (5440 days ago) |
| Assigned | 3/29/11 (5490 days ago) |
| Resolved | 5/18/11 (5440 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Version ⇒ Git master
State ⇒ Feedback
you create one?
Horde::debug();
before the error line, then check /tmp/horde_debug.txt
State ⇒ Unconfirmed
New Attachment: horde_cache_exception_detail.php
serialized data into a variable to make it easier to read.
Version ⇒ 4.0-RC1
State ⇒ Feedback
exception somewhere in the call stack.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Selecting SQL Cache on initial Horde config results in SQL Error
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
SQL-based cache. Upon saving, I got this message to the screen (and
in Horde's log):
3/26/11 3:39:01 PM HORDE[57515] HORDE QUERY FAILED: Table
'horde4.horde_cache' doesn't exist
INSERT INTO horde_cache... (details omitted)