[horde] No horde_imap_client_message table!

Federico Giannici giannici at neomedia.it
Sat May 28 15:20:39 UTC 2016


I just installed the latest version of Horde/IMP and I cannot get rid of 
two problems with the DBs.

One seems related to the limit to 1000 bytes (about 333 UTF-8 chars) of 
MySQL indexes (I'm using MariaDB 10.0.23).

But what I cannot really understand is the second one: there is no 
"horde_imap_client_message" table!

I executed lots of times the "horde-db-migrate" script, even deleted all 
tables and created them again, but always with this result:

[  INFO  ] Migrating DB up.
[  INFO  ] Current imp schema version: 3
[  INFO  ] Ending imp schema version: 3
[  INFO  ] Current ingo schema version: 7
[  INFO  ] Ending ingo schema version: 7
[  INFO  ] Current turba schema version: 11
[  INFO  ] Ending turba schema version: 11
[  INFO  ] Current content schema version: 2
[  INFO  ] Ending content schema version: 2
[  INFO  ] Current Horde_ActiveSync schema version: 22
[  INFO  ] Ending Horde_ActiveSync schema version: 22
[  INFO  ] Current Horde_Alarm schema version: 2
[  INFO  ] Ending Horde_Alarm schema version: 2
[  INFO  ] Current Horde_Auth schema version: 1
[  INFO  ] Ending Horde_Auth schema version: 1
[  INFO  ] Current Horde_Cache schema version: 2
[  INFO  ] Ending Horde_Cache schema version: 2
[  INFO  ] Current Horde_Core schema version: 1
[  INFO  ] Ending Horde_Core schema version: 1
[  INFO  ] Current Horde_Dav schema version: 1
Migrating to HordeDavRemoveUniqueIndex (2)
== 2 HordeDavRemoveUniqueIndex: migrating 
=====================================
-- removeIndex('horde_dav_objects', 'id_external')
    -> 0.0202s
-- addIndex('horde_dav_objects', 'id_external')
    -> 0.0028s
-- addIndex('horde_dav_objects', array(0 => 'id_external', 1 => 
'id_collection'), array('unique' => true))
QUERY FAILED: Specified key was too long; max key length is 1000 bytes

CREATE UNIQUE INDEX 
`index_horde_dav_objects_on_id_external_and_id_collection` ON 
`horde_dav_objects` (`id_external`, `id_collection`)
[  INFO  ] Current Horde_Group schema version: 3
[  INFO  ] Ending Horde_Group schema version: 3
[  INFO  ] Current Horde_History schema version: 6
[  INFO  ] Ending Horde_History schema version: 6
[  INFO  ] Current Horde_Imap_Client schema version: 1
Migrating to HordeImapClientChangeColumnName (2)
== 2 HordeImapClientChangeColumnName: migrating 
===============================
-- columns('horde_imap_client_data')
    -> 0.0250s
-- columns('horde_imap_client_message')
QUERY FAILED: Table 'horde3.horde_imap_client_message' doesn't exist

SHOW FIELDS FROM `horde_imap_client_message`
[  INFO  ] Current Horde_Lock schema version: 3
[  INFO  ] Ending Horde_Lock schema version: 3
[  INFO  ] Current Horde_Perms schema version: 3
[  INFO  ] Ending Horde_Perms schema version: 3
[  INFO  ] Current Horde_Prefs schema version: 3
[  INFO  ] Ending Horde_Prefs schema version: 3
[  INFO  ] Current Horde_Queue schema version: 1
[  INFO  ] Ending Horde_Queue schema version: 1
[  INFO  ] Current Horde_SessionHandler schema version: 2
[  INFO  ] Ending Horde_SessionHandler schema version: 2
[  INFO  ] Current Horde_Token schema version: 1
[  INFO  ] Ending Horde_Token schema version: 1
[  INFO  ] Current Horde_Vfs schema version: 4
[  INFO  ] Ending Horde_Vfs schema version: 4


What am I missing?

If anything, can anybody send my the "horde_imap_client_message" table 
structure?

Thanks.


More information about the horde mailing list