[horde] 'horde.horde_imap_client_message' doesn't exist

John H. Bennett III bennettj at thebennetthome.com
Sun Feb 23 02:44:42 UTC 2014


Quoting "John H. Bennett III" <bennettj at thebennetthome.com>:

> Quoting Jan Schneider <jan at horde.org>:
>
>>
>> Zitat von "John H. Bennett III" <bennettj at thebennetthome.com>:
>>
>>> Quoting Michael M Slusarz <slusarz at horde.org>:
>>>
>>>> Quoting "John H. Bennett III" <bennettj at thebennetthome.com>:
>>>>
>>>>> == 2 HordeImapClientChangeColumnName: migrating  
>>>>> ===============================
>>>>> -- columns('horde_imap_client_data')
>>>>> -> 0.0026s
>>>>> -- columns('horde_imap_client_message')
>>>>> QUERY FAILED: Table 'horde.horde_imap_client_message' doesn't exist
>>>>
>>>> horde_imap_client_message should exist.  It is in version 1 of  
>>>> the migration script, and I can verify it exists in my test  
>>>> setup.  If it doesn't, there is/was something wrong with your SQL  
>>>> tables.
>>>>
>>>> You can drop the tables for Horde_Imap_Client with the migration  
>>>> tool in horde and then re-add it, although be aware this will  
>>>> clear all cache data.
>>>>
>>>> michael
>>>> -- 
>>>>
>>> Well, anything else I can try?  This is a test server.
>>>
>>> root at dev ~]# php /usr/bin/horde-db-migrate Horde_Imap_Client down
>>> [  INFO  ] Migrating DB down.
>>> [  INFO  ] Current Horde_Imap_Client schema version: 1
>>> Migrating from HordeImapClientBaseTables (1)
>>> == 1 HordeImapClientBaseTables: reverting  
>>> =====================================
>>> -- dropTable('horde_imap_client_data')
>>> SQLSTATE[42S02]: Base table or view not found: 1051 Unknown table  
>>> 'horde_imap_client_data'
>>>
>>> [root at dev ~]# php /usr/bin/horde-db-migrate Horde_Imap_Client up
>>> [  INFO  ] Migrating DB up.
>>> [  INFO  ] Current Horde_Imap_Client schema version: 1
>>> Migrating to HordeImapClientChangeColumnName (2)
>>> == 2 HordeImapClientChangeColumnName: migrating  
>>> ===============================
>>> -- columns('horde_imap_client_data')
>>> SQLSTATE[42S02]: Base table or view not found: 1146 Table  
>>> 'horde.horde_imap_client_data' doesn't exist
>>> [root at dev ~]# php /usr/bin/horde-db-migrate Horde_Imap_Client version
>>> [  INFO  ] Migrating DB to schema version version.
>>>
>>> [  INFO  ] Current Horde_Imap_Client schema version: 1
>>> Reached target version: version
>>> [  INFO  ] Ending Horde_Imap_Client schema version: 1
>>>
>>> Thanks again,
>>>
>>> John
>>
>> Delete all tables starting with "horde_imap_client_" manually.
>> -- 
>> Jan Schneider
>> The Horde Project
>> http://www.horde.org/
>> https://www.facebook.com/hordeproject
>
> Thanks again for your time and help.  I just did this now.  Same issue.
>
> [  INFO  ] Current Horde_Imap_Client schema version: 0
> Migrating to HordeImapClientBaseTables (1)
> == 1 HordeImapClientBaseTables: migrating  
> =====================================
> -- tables()
>    -> 0.0020s
> -- createTable('horde_imap_client_data', array('autoincrementKey' =>  
> 'messageid'))
>    -> 0.0001s
> -- addIndex('horde_imap_client_data', array(0 => 'hostspec', 1 =>  
> 'mailbox', 2 => 'port', 3 => 'username'))
> SQLSTATE[42000]: Syntax error or access violation: 1071 Specified  
> key was too long; max key length is 1000 bytes
>
> Subsequent runs give me:
>
> Migrating to HordeImapClientBaseTables (1)
> == 1 HordeImapClientBaseTables: migrating  
> =====================================
> -- tables()
>    -> 0.0018s
> == 1 HordeImapClientBaseTables: migrated (0.0020s)  
> ============================
>
> Migrating to HordeImapClientChangeColumnName (2)
> == 2 HordeImapClientChangeColumnName: migrating  
> ===============================
> -- columns('horde_imap_client_data')
>    -> 0.0046s
> -- columns('horde_imap_client_message')
> SQLSTATE[42S02]: Base table or view not found: 1146 Table  
> 'horde.horde_imap_client_message' doesn't exist
>
> FWIW, I'm using mysql
> $conf['sql']['phptype'] = 'mysql';
>
> Changing to mysqli, doesn't help.
>
> [root at dev]# mysql -v
> Welcome to the MySQL monitor.  Commands end with ; or \g.
> Your MySQL connection id is 380
> Server version: 5.1.69 Source distribution
>
> John
>
>
I think I've finally found the issue.  I was using UTF-8 as the  
charset for mysql.  I found this bug,  
http://bugs.mysql.com/bug.php?id=4541.  Changing to latin1 fixes  
things and the horde DB's get updated.  Not sure when I changed to  
utf-8 unless that's the default, but my current horde 3 DB is using  
latin1 also, so for me I think It will fix all my issues, and allow me  
to begin upgrading without fear.

Hopefully, this can help someone else.

Appreciate everyone's time.

Thanks,

John





More information about the horde mailing list