Tickets :: Comment on [#12234] Horde

* Your Email Address
* Spam protection	Enter the letters below: . ..__ . .__ .__. \|_/ [__)\| [__)\| \| \| \\| \\|___\| \\|__\
Comment	> Hi Jan, > >> The error already tells you what to do! Use horde_cache instead of >> Horde_Cache. > > Yes, "who can read, has advantages" - so after done it right --> > > # horde-db-migrate horde_cache 1 > [ INFO ] Migrating DB to schema version 1. > [ INFO ] Current horde_cache schema version: 2 > Migrating from HordeCacheFixBlobLength (2) > == 2 HordeCacheFixBlobLength: reverting > ======================================= > == 2 HordeCacheFixBlobLength: reverted (0.0000s) > ============================== > > Reached target version: 1 > [ INFO ] Ending horde_cache schema version: 1 > [root@vml000060 migration]# horde-db-migrate horde_cache > [ INFO ] Migrating DB up. > [ INFO ] Current horde_cache schema version: 1 > Migrating to HordeCacheFixBlobLength (2) > == 2 HordeCacheFixBlobLength: migrating > ======================================= > -- changeColumn('horde_cache', 'cache_data', 'binary') > -> 0.4488s > == 2 HordeCacheFixBlobLength: migrated (0.4492s) > ============================== > > [ INFO ] Ending horde_cache schema version: 2 > [root@vml000060 migration]# horde-db-migrate horde_cache 2 > [ INFO ] Migrating DB to schema version 2. > [ INFO ] Current horde_cache schema version: 2 > [ INFO ] Ending horde_cache schema version: 2 > > But, when I check the structur (with phpMyAdmin), its always this: > > -- > -- Tabellenstruktur für Tabelle `horde_cache` > -- > > 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; > > What's my fault? > > Thank you! > Klaus.
Attachment
Watch this ticket

Saved Queries