[Tickets #12234] Horde_cache DB schema

noreply at bugs.horde.org noreply at bugs.horde.org
Thu May 2 22:21:55 UTC 2013


BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/12234
------------------------------------------------------------------------------
  Ticket           | 12234
  Erstellt Von     | klaus at tachtler.net
  Zusammenfassung  | Horde_cache DB schema
  Warteschlange    | Horde Framework Packages
  Version          | Git master
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


klaus at tachtler.net (2013-05-02 22:21) hat geschrieben:

Hi,

i installed horde from a long time ago (Horde 4) an upgrade to Horde 5.

After upgrade Horde_cache to Version 2.1.0, i checked the DB schema and the
table horde_cache structure looks like this:

CREATE TABLE IF NOT EXISTS `horde_cache` (
   `cache_id` varchar(32) NOT NULL,
   `cache_timestamp` bigint(20) NOT NULL,
   `cache_expiration` bigint(20) NOT NULL,
   `cache_data` blob,
   PRIMARY KEY (`cache_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Is that correct? - Or should it be like that:

CREATE TABLE horde_cache (
     cache_id          VARCHAR(32) NOT NULL,
     cache_timestamp   BIGINT NOT NULL,
     cache_data        LONGBLOB,
-- Or, on some DBMS systems:
--  cache_data        IMAGE,

     PRIMARY KEY  (cache_id)
);

I use MySQL (msqli) as backend system for Cache on Horde.

Thank you,
Klaus.






More information about the bugs mailing list